From: Johannes Berg <johannes@sipsolutions.net>
To: Tomas Winkler <tomasw@gmail.com>
Cc: linville@tuxdriver.com, yi.zhu@intel.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/1] mac80211: filter probes in ieee80211_rx_mgmt_probe_resp
Date: Tue, 05 Aug 2008 11:09:08 +0200 [thread overview]
Message-ID: <1217927348.3603.29.camel@johannes.berg> (raw)
In-Reply-To: <1ba2fa240808050014t6e315fe5s607aff1656c1f8d1@mail.gmail.com> (sfid-20080805_091410_511567_4BA0F990)
[-- Attachment #1: Type: text/plain, Size: 997 bytes --]
On Tue, 2008-08-05 at 10:14 +0300, Tomas Winkler wrote:
> On Sun, Aug 3, 2008 at 9:14 PM, Johannes Berg <johannes@sipsolutions.net> wrote:
> > On Sun, 2008-08-03 at 14:32 +0300, Tomas Winkler wrote:
> >> This patch moves filtering statement from ieee80211_rx_bss_info
> >> which is called for both beacon and probe to ieee80211_rx_mgmt_probe_resp
> >> and save few cycles in beacon parsing.
> >
> > Sounds alright to me, but maybe we should then document that
> > rx_bss_info() only expects data for the right BSSID?
>
> Probes are filtered on destination address not on BSSID, to exclude
> probe responses not directed to the station.
> bss_info treats any BSSID this is what creates the bss list after all
> if I'm not mistaken.
Eh, right, of course, not sure why I got confused there. Still though,
adding a few lines of comments would be nice. If we did that every time
we changed a function, we'd have documentation for all functions in no
time ;) Oh well...
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2008-08-05 9:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-03 11:32 [PATCH 1/1] mac80211: filter probes in ieee80211_rx_mgmt_probe_resp Tomas Winkler
2008-08-03 18:14 ` Johannes Berg
2008-08-05 7:14 ` Tomas Winkler
2008-08-05 9:09 ` Johannes Berg [this message]
2008-08-05 15:21 ` Tomas Winkler
2008-08-05 15:27 ` Johannes Berg
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=1217927348.3603.29.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=tomasw@gmail.com \
--cc=yi.zhu@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