+ linux-wireless, Johannes
On 26-3-2016 11:28, Kalle Valo wrote:
> Arend van Spriel <[email protected]> writes:
>
>> This brcmfmac patch [1] is set to "Awaiting Upstream" as it relies on
>> nl80211 patch. However, that patch was already in linux-next before the
>> merge window so are you waiting for 4.6-rc1 or did you miss this one?
>> Just want to understand the use of this state.
>>
>> Regards,
>> Arend
>>
>> [1] https://patchwork.kernel.org/patch/8484901/
>
> Commit 0a87cadbb54e is not in net-next yet, I guess Johannes didn't send
> a pull request yet. Once it's in net-next it needs come down to
> wireless-drivers-next before I can apply it. So I'm waiting for that.
Ah. I figured the patch made it to the 4.6 deadline, but apparently not.
> But please do remind about this, I seldomly check the "Awaiting
> Upstream" queue so sometimes it might take way too long before I apply
> the patch.
So this is another way of saying the author should keep an eye on his
patches when it ends up in this state or in general ;-) Noted.
Thanks,
Arend
Arend Van Spriel <[email protected]> writes:
>> But please do remind about this, I seldomly check the "Awaiting
>> Upstream" queue so sometimes it might take way too long before I apply
>> the patch.
>
> So this is another way of saying the author should keep an eye on his
> patches when it ends up in this state or in general ;-) Noted.
Yeah, exactly :) Especially it's very helpful to send a note once the
dependency is in wireless-drivers-next, otherwise I need to manually
check and unsurprisingly I don't do it that often...
--
Kalle Valo