All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: agreen@cococorp.com
Cc: linux-wireless@vger.kernel.org, Jesse Jones <jjones@cococorp.com>
Subject: Re: [PATCH v2]: mac80211: Always check rates and capabilities in mesh mode
Date: Tue, 09 Jun 2015 22:05:22 +0200	[thread overview]
Message-ID: <1433880322.1892.22.camel@sipsolutions.net> (raw)
In-Reply-To: <557745EB.9080907@cococorp.com> (sfid-20150609_220053_201960_F15CC300)

On Tue, 2015-06-09 at 13:00 -0700, Alexis Green wrote:
> In mesh mode there is a race between establishing links and processing
> rates and capabilities in beacons. This is very noticeable with slow
> beacons (e.g. beacon intervals of 1s) and manifested for us as stations
> using minstrel when minstrel_ht should be used. Fixed by changing
> mesh_sta_info_init so that it always checks rates and such if it has not
> already done so.

Applied.

johannes


      reply	other threads:[~2015-06-09 20:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-09 20:00 [PATCH v2]: mac80211: Always check rates and capabilities in mesh mode Alexis Green
2015-06-09 20:05 ` 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=1433880322.1892.22.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=agreen@cococorp.com \
    --cc=jjones@cococorp.com \
    --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 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.