Linux wireless drivers development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Vasanthakumar Thiagarajan <vasanth@atheros.com>
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, 03 Feb 2009 11:24:21 +0100	[thread overview]
Message-ID: <1233656661.5460.4.camel@johannes.local> (raw)
In-Reply-To: <20090203101911.GC8246@vasanth-laptop>

[-- Attachment #1: Type: text/plain, Size: 891 bytes --]

On Tue, 2009-02-03 at 15:49 +0530, Vasanthakumar Thiagarajan wrote:
> 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.

Not just that, but also when we've found a BSS and never connect to it,
we'll never time it out. It's nothing you need to fix though, I'm
perfectly ok with just putting this patch in as a start.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      reply	other threads:[~2009-02-03 10:24 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
2009-02-03 10:24     ` 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=1233656661.5460.4.camel@johannes.local \
    --to=johannes@sipsolutions.net \
    --cc=Vasanth.Thiagarajan@Atheros.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=vasanth@atheros.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