From: Johannes Berg <johannes@sipsolutions.net>
To: Bala Shanmugam <bkamatch@qca.qualcomm.com>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] cfg80211: Add background scan period attribute.
Date: Wed, 29 Feb 2012 13:39:14 +0100 [thread overview]
Message-ID: <1330519154.4714.6.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <1330518896-15230-1-git-send-email-bkamatch@qca.qualcomm.com> (sfid-20120229_133516_521752_BEEDD972)
On Wed, 2012-02-29 at 18:04 +0530, Bala Shanmugam wrote:
> Receive background scan period as part of connect
> command and pass the same to driver.
>
> Signed-off-by: Bala Shanmugam <bkamatch@qca.qualcomm.com>
> ---
> include/linux/nl80211.h | 8 ++++++++
> include/net/cfg80211.h | 2 ++
> net/wireless/nl80211.c | 7 +++++++
> net/wireless/wext-sme.c | 5 +++++
> 4 files changed, 22 insertions(+), 0 deletions(-)
>
> diff --git a/include/linux/nl80211.h b/include/linux/nl80211.h
> index ad56e21..7cef223 100644
> --- a/include/linux/nl80211.h
> +++ b/include/linux/nl80211.h
> @@ -367,6 +367,9 @@
> * %NL80211_ATTR_WIPHY_FREQ, %NL80211_ATTR_CONTROL_PORT,
> * %NL80211_ATTR_CONTROL_PORT_ETHERTYPE and
> * %NL80211_ATTR_CONTROL_PORT_NO_ENCRYPT.
> + * Background scan period can also be
> + * optionally specified in %NL80211_ATTR_BG_SCAN_PERIOD.
> + * If period value is 0, bg scan will be disabled.
Nack. We leave out the attribute in those cases and make 0 an invalid
value.
Also please have this reviewed internally first. I'm tired of pointing
out all the whitespace, code formatting, etc. issues from QCA folks.
johannes
next prev parent reply other threads:[~2012-02-29 12:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 12:34 [PATCH] cfg80211: Add background scan period attribute Bala Shanmugam
2012-02-29 12:39 ` Johannes Berg [this message]
2012-02-29 14:02 ` bkamatch
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=1330519154.4714.6.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=bkamatch@qca.qualcomm.com \
--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 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).