linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: "Pedersen, Thomas" <c_tpeder@qca.qualcomm.com>
Cc: Holger Schurig <holgerschurig@googlemail.com>,
	kvalo@qca.qualcomm.com, ath6kl-devel@qualcomm.com,
	linux-wireless@vger.kernel.org
Subject: Re: [PATCH] nl80211: specify RSSI threshold when scanning
Date: Thu, 14 Jun 2012 08:48:52 +0200	[thread overview]
Message-ID: <1339656532.4909.0.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <20120613204537.GA3043@pista>

On Wed, 2012-06-13 at 13:45 -0700, Pedersen, Thomas wrote:
> On Wed, Jun 13, 2012 at 07:53:51AM +0200, Holger Schurig wrote:
> > @NL80211_ATTR_SCHED_SCAN_MATCH_RSSI
> > 
> > I'd also move around "SCHED" and "ATTR". Look at the attribute names
> > above or below it, then it's more obvious:
> > 
> > NL80211_SCHED_SCAN_MATCH_ATTR_SSID
> > NL80211_ATTR_SCHED_SCAN_MATCH_RSSI
> > NL80211_SCHED_SCAN_MATCH_ATTR_MAX
> 
> Makes sense. In wireless-testing HEAD the SSID match attr is actually
> "NL80211_ATTR_SCHED_SCAN_MATCH_SSID".

I just fixed that :)

johannes


  reply	other threads:[~2012-06-14  6:48 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-12 20:43 [PATCH] nl80211: specify RSSI threshold when scanning Thomas Pedersen
2012-06-13  5:40 ` Johannes Berg
2012-06-13  5:53   ` Holger Schurig
2012-06-13  5:54     ` Johannes Berg
2012-06-13 20:45     ` Pedersen, Thomas
2012-06-14  6:48       ` Johannes Berg [this message]
2012-06-13 11:37   ` Luciano Coelho
2012-06-13 11:56     ` Kalle Valo
2012-06-13 20:50       ` Pedersen, Thomas
2012-06-13 21:05         ` Luciano Coelho
2012-06-14  6:29         ` Kalle Valo
2012-06-14 19:39           ` Chadd, Adrian
2012-06-14 20:21             ` Singh, Naveen
2012-06-14 20:41               ` Chadd, Adrian
2012-06-14 21:18                 ` Singh, Naveen
2012-06-14 22:16                   ` Chadd, Adrian
2012-06-15  4:40                     ` Luciano 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=1339656532.4909.0.camel@jlt3.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=ath6kl-devel@qualcomm.com \
    --cc=c_tpeder@qca.qualcomm.com \
    --cc=holgerschurig@googlemail.com \
    --cc=kvalo@qca.qualcomm.com \
    --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;
as well as URLs for NNTP newsgroup(s).