From: Vasanthakumar Thiagarajan <vasanth@atheros.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Vasanth Thiagarajan <Vasanth.Thiagarajan@Atheros.com>,
"linville@tuxdriver.com" <linville@tuxdriver.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v2] mac80211: Remove bss information of the current AP when it goes out of range
Date: Tue, 3 Feb 2009 15:49:11 +0530 [thread overview]
Message-ID: <20090203101911.GC8246@vasanth-laptop> (raw)
In-Reply-To: <1233655853.5460.0.camel@johannes.local>
On Tue, Feb 03, 2009 at 03:40:53PM +0530, Johannes Berg wrote:
> On Tue, 2009-02-03 at 10:09 +0530, Vasanthakumar Thiagarajan wrote:
> > There is no point having the bss information of currently associated AP
> > when the AP is detected to be out of range.
>
> Seems sane to me. There are a few other places I think where we hold on
> to the bss info way too long, in fact, we hold on to it _forever_ most
> of the time.
>
Yeah, we hold bss info when we get direct probe timeout, auth timeout and assoc
timeout. I will remove bss in those places also n the next version.
Thanks,
Vasanth
next prev parent reply other threads:[~2009-02-03 10:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-03 4:39 [PATCH v2] mac80211: Remove bss information of the current AP when it goes out of range Vasanthakumar Thiagarajan
2009-02-03 10:10 ` Johannes Berg
2009-02-03 10:19 ` Vasanthakumar Thiagarajan [this message]
2009-02-03 10:24 ` 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=20090203101911.GC8246@vasanth-laptop \
--to=vasanth@atheros.com \
--cc=Vasanth.Thiagarajan@Atheros.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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