From: Johannes Berg <johannes@sipsolutions.net>
To: Emmanuel Grumbach <emmanuel.grumbach@intel.com>
Cc: linux-wireless@vger.kernel.org, Sara Sharon <sara.sharon@intel.com>
Subject: Re: [PATCH] mac80211: ignore invalid scan RSSI values
Date: Tue, 09 Jun 2015 21:52:36 +0200 [thread overview]
Message-ID: <1433879556.1892.19.camel@sipsolutions.net> (raw)
In-Reply-To: <1433317457-6311-1-git-send-email-emmanuel.grumbach@intel.com>
On Wed, 2015-06-03 at 10:44 +0300, Emmanuel Grumbach wrote:
> From: Sara Sharon <sara.sharon@intel.com>
>
> Channels in 2.4GHz band overlap, this means that if we
> send a probe request on channel 1 and then move to channel
> 2, we will hear the probe response on channel 2. In this
> case, the RSSI will be lower than if we had heard it on
> the channel on which it was sent (1 in this case).
>
> The scan result ignores those invalid values and the
> station last signal should not be updated as well.
Applied.
johannes
prev parent reply other threads:[~2015-06-09 19:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-03 7:44 [PATCH] mac80211: ignore invalid scan RSSI values Emmanuel Grumbach
2015-06-09 19:52 ` Johannes Berg [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=1433879556.1892.19.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=emmanuel.grumbach@intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=sara.sharon@intel.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).