Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1633028 > unrolled thread

Re: [4/4] mwifiex: pcie: de-duplicate buffer allocation code

Started byBrian Norris <briannorris@chromium.org>
First post2017-04-28 19:00 +0200
Last post2017-05-04 15:20 +0200
Articles 2 — 2 participants

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [4/4] mwifiex: pcie: de-duplicate buffer allocation code Brian Norris <briannorris@chromium.org> - 2017-04-28 19:00 +0200
    Re: [4/4] mwifiex: pcie: de-duplicate buffer allocation code Kalle Valo <kvalo@codeaurora.org> - 2017-05-04 15:20 +0200

#1633028 — Re: [4/4] mwifiex: pcie: de-duplicate buffer allocation code

FromBrian Norris <briannorris@chromium.org>
Date2017-04-28 19:00 +0200
SubjectRe: [4/4] mwifiex: pcie: de-duplicate buffer allocation code
Message-ID<tBhpo-1F2-17@gated-at.bofh.it>
On Tue, Mar 21, 2017 at 02:14:05PM +0200, Kalle Valo wrote:
> What I could do is to wait for the patches 1-3 trickle down to w-d-next
> and then apply this patch. It usually takes few weeks, but with bad luck
> it might happen only after the merge window. Would that work?

Is this going to get picked up?

Brian

[toc] | [next] | [standalone]


#1635725

FromKalle Valo <kvalo@codeaurora.org>
Date2017-05-04 15:20 +0200
Message-ID<tDoPL-3W2-5@gated-at.bofh.it>
In reply to#1633028
Brian Norris <briannorris@chromium.org> writes:

> On Tue, Mar 21, 2017 at 02:14:05PM +0200, Kalle Valo wrote:
>> What I could do is to wait for the patches 1-3 trickle down to w-d-next
>> and then apply this patch. It usually takes few weeks, but with bad luck
>> it might happen only after the merge window. Would that work?
>
> Is this going to get picked up?

Oh man, I thought I had changed the state of this patch from Changes
Requested to Awaiting Upstream but apparently I didn't do that and hence
missed the patch. It's now back in active my queue in Under Review
state:

https://patchwork.kernel.org/patch/9618309/

Thanks for reminding me and sorry for the screwup.

-- 
Kalle Valo

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web