From: Johannes Berg <johannes@sipsolutions.net>
To: Eliad Peller <eliad@wizery.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Raja Mani <rmani@qti.qualcomm.com>
Subject: Re: [PATCH] nl80211: fix scheduled scan RSSI matchset attribute confusion
Date: Mon, 27 Jan 2014 09:19:25 +0100 [thread overview]
Message-ID: <1390810765.4251.0.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <CAB3XZEc94pTAMXWPYeWhu7o_YLEnD1_9O035-+YXYiR0Uij28w@mail.gmail.com> (sfid-20140126_095646_302413_1A037FFE)
On Sun, 2014-01-26 at 10:56 +0200, Eliad Peller wrote:
> this means that min-rssi-only sched scan request will be seen as
> req->n_match_sets = 1 with empty SSID?
Yes.
> i don't think that's desirable (at least the current documentation
> assumes n_match_sets=0 for this case).
I don't think that's true? I looked at the drivers that use this and
they all skip empty SSIDs, except the one that I fixed.
johannes
next prev parent reply other threads:[~2014-01-27 8:19 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
2014-01-25 9:19 ` Mani, Raja
2014-01-26 8:56 ` Eliad Peller
2014-01-27 8:19 ` Johannes Berg [this message]
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=1390810765.4251.0.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=eliad@wizery.com \
--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).