From: Johannes Berg <johannes@sipsolutions.net>
To: "Mani, Raja" <rmani@qti.qualcomm.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] nl80211: fix scheduled scan RSSI matchset attribute confusion
Date: Sat, 25 Jan 2014 09:40:11 +0100 [thread overview]
Message-ID: <1390639211.4131.1.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <BD8355E3EE4C424D96D29100D45098AB42C43A80@aphydexd01a.ap.qualcomm.com>
On Sat, 2014-01-25 at 05:46 +0000, Mani, Raja wrote:
> >@@ -5669,15 +5708,28 @@ static int nl80211_start_sched_scan(struct sk_buff *skb,
> > nla_data(ssid), nla_len(ssid));
> > request->match_sets[i].ssid.ssid_len =
> > nla_len(ssid);
> >+ /* special attribute - old implemenation w/a */
> >+ request->match_sets[i].rssi_thold =
> >+ default_match_rssi;
>
> How about this case where RSSI is disabled for SSID1 and and SSID 4
> and only SSID2 and SSID3 needs RSSI filter.
>
> SSID1, SSID2, RSSI, SSID3, RSSI, SSID4
>
> Wouldn't this change set RSSI of SSID3 to SSID1 and SSID4 ?
> Did i miss to understand anything ?
It's not a case that was previously supported. Previously, all you could
do was
{ SSID1 | SSID2 | SSID3 } + RSSI
Now, you can do
{ (SSID1, RSSI1) | (SSID2, RSSI2) | (SSID3, RSSI3) }
IOW, it wouldn't change anything - note how the RSSI value before used
to set request->rssi_thold, and not request->matchsets[i].rssi_thold.
johannes
next prev parent reply other threads:[~2014-01-25 8:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-24 12:20 [PATCH] nl80211: fix scheduled scan RSSI matchset attribute confusion Johannes Berg
2014-01-25 5:46 ` Mani, Raja
2014-01-25 8:40 ` Johannes Berg [this message]
2014-01-25 9:19 ` Mani, Raja
2014-01-26 8:56 ` Eliad Peller
2014-01-27 8:19 ` Johannes Berg
2014-01-27 9:37 ` Eliad Peller
2014-01-29 12:17 ` Johannes Berg
2014-01-29 12:31 ` Johannes Berg
2014-02-02 8:04 ` Eliad Peller
2014-02-03 10:09 ` Johannes Berg
2014-02-03 10:43 ` Eliad Peller
-- strict thread matches above, loose matches on Subject: below --
2014-02-03 10:10 Johannes Berg
2014-01-24 10:01 Johannes Berg
2014-01-24 10:24 ` Luca Coelho
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=1390639211.4131.1.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=rmani@qti.qualcomm.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).