From: Johannes Berg <johannes@sipsolutions.net>
To: arend@broadcom.com
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH V11 1/2] nl80211: add feature for BSS selection support
Date: Fri, 04 Mar 2016 10:13:25 +0100 [thread overview]
Message-ID: <1457082805.2333.0.camel@sipsolutions.net> (raw)
In-Reply-To: <56D8A618.4050707@broadcom.com> (sfid-20160303_220118_206425_01EF95D1)
On Thu, 2016-03-03 at 22:01 +0100, Arend Van Spriel wrote:
>
> On 3-3-2016 16:55, Johannes Berg wrote:
> > On Wed, 2016-03-02 at 20:37 +0100, Arend van Spriel wrote:
> > > Introducing a new feature that the driver can use to
> > > indicate the driver/firmware supports configuration of BSS
> > > selection criteria upon CONNECT command. This can be useful
> > > when multiple BSS-es are found belonging to the same ESS,
> > > ie. Infra-BSS with same SSID. The criteria can then be used to
> > > offload selection of a preferred BSS.
> > >
> > Applied, finally :)
> >
> > I moved the wiphy supported methods check into parse_bss_select()
> > to
> > avoid the double error path in the caller, plus some editorial
> > changes.
>
> Do you expect Kalle to take the brcmfmac patch or can it go through
> your tree?
>
I was expecting Kalle to apply it.
johannes
next prev parent reply other threads:[~2016-03-04 9:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-02 19:37 [PATCH V11 1/2] nl80211: add feature for BSS selection support Arend van Spriel
2016-03-02 19:37 ` [PATCH V11 2/2] brcmfmac: add support for nl80211 BSS_SELECT feature Arend van Spriel
2016-03-07 12:52 ` Kalle Valo
2016-03-07 19:46 ` Arend Van Spriel
2016-04-15 18:33 ` Kalle Valo
2016-04-17 14:37 ` Arend van Spriel
2016-04-18 16:13 ` Kalle Valo
2016-04-17 14:44 ` [PATCH V11] " Arend van Spriel
2016-04-26 9:14 ` [V11] " Kalle Valo
2016-03-03 15:55 ` [PATCH V11 1/2] nl80211: add feature for BSS selection support Johannes Berg
2016-03-03 19:19 ` Arend Van Spriel
2016-03-03 21:01 ` Arend Van Spriel
2016-03-04 9:13 ` Johannes Berg [this message]
2016-03-04 14:38 ` Kalle Valo
2016-03-04 20:03 ` Arend Van Spriel
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=1457082805.2333.0.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arend@broadcom.com \
--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).