From: Johannes Berg <johannes@sipsolutions.net>
To: Bing Zhao <bzhao@marvell.com>
Cc: linux-wireless@vger.kernel.org, Jouni Malinen <j@w1.fi>,
"John W. Linville" <linville@tuxdriver.com>,
Amitkumar Karwar <akarwar@marvell.com>
Subject: Re: [PATCH v2] nl/cfg80211: advertise OBSS scan offload capability
Date: Mon, 12 Nov 2012 10:31:37 +0100 [thread overview]
Message-ID: <1352712697.9525.4.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1352512290-7316-1-git-send-email-bzhao@marvell.com>
On Fri, 2012-11-09 at 17:51 -0800, Bing Zhao wrote:
> From: Amitkumar Karwar <akarwar@marvell.com>
>
> wpa_supplicant will do OBSS scan for drivers that implement
> auth/assoc API. Drivers that implement nl80211 connect API
> (rather than auth/assoc) may need wpa_supplicant to do this
> as well.
>
> New flag is added to inform userspace that this driver will
> make use of wpa_supplicant's OBSS scan feature.
> + * @NL80211_FEATURE_OBSS_SCAN_OFFLOAD: The driver expects user space to
> + * perform OBSS scan and generate 20/40 BSS coex reports. This flag is
> + * interested in only in the case of a driver that has connect API.
Applied, but I changed a lot ;-)
Notably, I reworded the constant name to be
NL80211_FEATURE_NEED_OBSS_SCAN, since we typically use the term
"offload" to mean that the *device* does something, not to mean that
*userspace* does something.
johannes
next prev parent reply other threads:[~2012-11-12 9:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-10 1:51 [PATCH v2] nl/cfg80211: advertise OBSS scan offload capability Bing Zhao
2012-11-12 9:31 ` Johannes Berg [this message]
2012-11-12 11:17 ` Jouni Malinen
2012-11-12 11:42 ` Johannes Berg
2012-11-12 21:38 ` Bing Zhao
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=1352712697.9525.4.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=akarwar@marvell.com \
--cc=bzhao@marvell.com \
--cc=j@w1.fi \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.