From: Johannes Berg <johannes@sipsolutions.net>
To: Bing Zhao <bzhao@marvell.com>
Cc: linux-wireless@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>,
Sam Leffler <sleffler@chromium.org>,
Amitkumar Karwar <akarwar@marvell.com>,
Avinash Patil <patila@marvell.com>,
Nishant Sarmukadam <nishants@marvell.com>,
Frank Huang <frankh@marvell.com>
Subject: Re: [PATCH v3 2/5] cfg80211: add scan flag to indicate its priority
Date: Wed, 10 Oct 2012 10:16:02 +0200 [thread overview]
Message-ID: <1349856962.4683.30.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1349326066-28501-3-git-send-email-bzhao@marvell.com>
On Wed, 2012-10-03 at 21:47 -0700, Bing Zhao wrote:
> v3: Add WIPHY_FLAG_LOW_PRIORITY_SCAN flag so that device can advertise
> low priority scan capability. An error will be returned to the
> application if device doesn't support this feature.
> Flush scan table feature is by default enabled.
> (Johannes Berg)
Great, but you're not advertising it to userspace? I think that should
be there so it can know whether it can request flush etc?
Also, how should flush really work with scheduled scan? Or should it be
documented to not work there?
johannes
next prev parent reply other threads:[~2012-10-10 8:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-04 4:47 [PATCH v3 0/5] add scan flags support Bing Zhao
2012-10-04 4:47 ` [PATCH v3 1/5] {nl,cfg}80211: add a flags word to scan requests Bing Zhao
2012-10-04 4:47 ` [PATCH v3 2/5] cfg80211: add scan flag to indicate its priority Bing Zhao
2012-10-10 8:16 ` Johannes Berg [this message]
2012-10-04 4:47 ` [PATCH v3 3/5] cfg80211: code rearrangement to avoid forward declarations Bing Zhao
2012-10-04 4:47 ` [PATCH v3 4/5] cfg80211: add support for flushing old scan results Bing Zhao
2012-10-04 4:47 ` [PATCH v3 5/5] mac80211: add support for tx to abort low priority scan requests Bing Zhao
2012-10-10 8:18 ` [PATCH v3 0/5] add scan flags support Johannes Berg
2012-10-10 13:56 ` Amitkumar Karwar
2012-10-11 12:14 ` Johannes Berg
2012-10-11 12:29 ` Amitkumar Karwar
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=1349856962.4683.30.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=akarwar@marvell.com \
--cc=bzhao@marvell.com \
--cc=frankh@marvell.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=nishants@marvell.com \
--cc=patila@marvell.com \
--cc=sleffler@chromium.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