From: Rajkumar Manoharan <rmanohar@qca.qualcomm.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: <linux-wireless@vger.kernel.org>
Subject: Re: [RFC] wireless: Do not allow disabled channel in scan request
Date: Thu, 15 Sep 2011 17:38:47 +0530 [thread overview]
Message-ID: <20110915120846.GA4025@vmraj-lnx.users.atheros.com> (raw)
In-Reply-To: <1316088306.3992.10.camel@jlt3.sipsolutions.net>
On Thu, Sep 15, 2011 at 02:05:06PM +0200, Johannes Berg wrote:
> On Thu, 2011-09-15 at 17:33 +0530, Rajkumar Manoharan wrote:
> > cfg80211_conn_scan allows disabled channels at scan request.
> > Hence probe request was seen at the disabled one. This patch
> > ensures that disabled channel never be added into the scan
> > request's channel list.
>
> Acked-by: Johannes Berg <johannes@sipsolutions.net>
>
> Good catch. We should probably refactor this later to go through a
> single point...
>
True. Thanks for the review
--
Rajkumar
prev parent reply other threads:[~2011-09-15 12:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-15 12:03 [RFC] wireless: Do not allow disabled channel in scan request Rajkumar Manoharan
2011-09-15 12:05 ` Johannes Berg
2011-09-15 12:08 ` Rajkumar Manoharan [this message]
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=20110915120846.GA4025@vmraj-lnx.users.atheros.com \
--to=rmanohar@qca.qualcomm.com \
--cc=johannes@sipsolutions.net \
--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