All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jouni Malinen <j@w1.fi>
To: Alina Friedrichsen <x-alina@gmx.net>
Cc: linux-wireless@vger.kernel.org, linville@tuxdriver.com
Subject: Re: [PATCH] Fixed BSSID step 3: Don't merge with the same BSSID
Date: Mon, 12 Jan 2009 19:35:26 +0200	[thread overview]
Message-ID: <20090112173526.GA18470@jm.kir.nu> (raw)
In-Reply-To: <20090112041534.24150@gmx.net>

On Mon, Jan 12, 2009 at 05:15:34AM +0100, Alina Friedrichsen wrote:
> > For the particular problem that you are
> > seeing, the minimal change would probably be just to make
> > sta_info_flush_delayed() call conditional on SSID change (I don't think
> > this would need to be based on BSSID change).
> 
> If the others agree, I can implement it in the end of the week. Or do you want it the other way?
> I personally don't want change too much...?

Of course I would like to have the full cleanup in the long run, but I
have nothing against first doing the minimal change to fix the
identified issue.

-- 
Jouni Malinen                                            PGP id EFC895FA

  reply	other threads:[~2009-01-12 17:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-06  2:01 [PATCH] Fixed BSSID step 3: Don't merge with the same BSSID Alina Friedrichsen
2009-01-08  9:10 ` Jouni Malinen
2009-01-09 20:53   ` Alina Friedrichsen
2009-01-10  9:16     ` Jouni Malinen
2009-01-12  4:15       ` Alina Friedrichsen
2009-01-12 17:35         ` Jouni Malinen [this message]
2009-01-17  3:39       ` [PATCH] Fixed BSSID (timesync) Alina Friedrichsen
2009-01-17  3:51       ` Alina Friedrichsen
2009-01-17 22:12   ` [PATCH] Fixed BSSID step 3: Don't merge with the same BSSID Alina Friedrichsen
2009-01-20 15:10     ` Jouni Malinen
2009-01-20 18:56       ` Alina Friedrichsen
2009-01-21  8:45         ` Jouni Malinen

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=20090112173526.GA18470@jm.kir.nu \
    --to=j@w1.fi \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=x-alina@gmx.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.