public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Benoit Papillault <benoit.papillault@free.fr>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] mac80211: Improved IBSS merges
Date: Fri, 05 Feb 2010 11:32:57 +0100	[thread overview]
Message-ID: <1265365977.3613.2.camel@johannes.local> (raw)
In-Reply-To: <1265319990-25583-1-git-send-email-benoit.papillault@free.fr>

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

On Thu, 2010-02-04 at 22:46 +0100, Benoit Papillault wrote:

> Next, we merge even if the BSSID from the received beacon is the same as
> our since merge can update more things that BSSID itself. This is
> specifically true for ath9k where the merge updates TBTT timers as a
> side effect and this is indeed needed if the TSF has been updated (if
> TSF is updated, we need to update TBTT timers as well).

> @@ -373,10 +370,6 @@ static void ieee80211_rx_bss_info(struct ieee80211_sub_if_data *sdata,
>  				sdata->u.ibss.ssid_len))
>  		goto put_bss;
>  
> -	/* same BSSID */
> -	if (memcmp(cbss->bssid, sdata->u.ibss.bssid, ETH_ALEN) == 0)
> -		goto put_bss;
> -
>  	if (rx_status->flag & RX_FLAG_TSFT) {
>  		/*
>  		 * For correct IBSS merging we need mactime; since mactime is

NACK. This will create merges and merges and merges and merges whenever
you use hardware that doesn't have accurate timestamps all the time.

johannes

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

  reply	other threads:[~2010-02-05 10:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-04 21:46 [PATCH] mac80211: Improved IBSS merges Benoit Papillault
2010-02-05 10:32 ` Johannes Berg [this message]
2010-02-05 14:37   ` Benoit PAPILLAULT
2010-02-05 15:02     ` 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=1265365977.3613.2.camel@johannes.local \
    --to=johannes@sipsolutions.net \
    --cc=benoit.papillault@free.fr \
    --cc=linux-wireless@vger.kernel.org \
    /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