From: Arend Van Spriel <arend.vanspriel@broadcom.com>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
Johannes Berg <johannes@sipsolutions.net>
Subject: Re: [V11,2/2] brcmfmac: add support for nl80211 BSS_SELECT feature
Date: Tue, 29 Mar 2016 10:46:53 +0200 [thread overview]
Message-ID: <56FA40FD.3040609@broadcom.com> (raw)
In-Reply-To: <87pouhcz3a.fsf@kamboji.qca.qualcomm.com>
+ linux-wireless, Johannes
On 26-3-2016 11:28, Kalle Valo wrote:
> Arend van Spriel <arend.vanspriel@broadcom.com> 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
next parent reply other threads:[~2016-03-29 8:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <56F65580.4060403@broadcom.com>
[not found] ` <87pouhcz3a.fsf@kamboji.qca.qualcomm.com>
2016-03-29 8:46 ` Arend Van Spriel [this message]
2016-03-30 12:19 ` [V11,2/2] brcmfmac: add support for nl80211 BSS_SELECT feature Kalle Valo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56FA40FD.3040609@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=johannes@sipsolutions.net \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).