linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jouni Malinen <j@w1.fi>
To: Alina Friedrichsen <x-alina@gmx.net>
Cc: linux-wireless@vger.kernel.org, johannes@sipsolutions.net
Subject: Re: [PATCH] Fixed BSSID step 3: Don't merge with the same BSSID
Date: Wed, 21 Jan 2009 10:45:09 +0200	[thread overview]
Message-ID: <20090121084509.GA11265@jm.kir.nu> (raw)
In-Reply-To: <20090120185635.284250@gmx.net>

On Tue, Jan 20, 2009 at 07:56:35PM +0100, Alina Friedrichsen wrote:

> Okay, thanks for your notice. Than I think the dummy merge detection code should in the ieee80211_sta_join_ibss() function and if so only call reset_tsf()?!
> Should it make any other thinks too in this case?

That is probably enough, but I have to admit I have not gone through all
the details here. It certainly should not need to remove existing STA
entries or reconfigure beacon data etc. that may have been there in the
past.

-- 
Jouni Malinen                                            PGP id EFC895FA

      reply	other threads:[~2009-01-21  8:45 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
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 [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=20090121084509.GA11265@jm.kir.nu \
    --to=j@w1.fi \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --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 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).