From: Johannes Berg <johannes@sipsolutions.net>
To: Ben Greear <greearb@candelatech.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: rate mask resulting in no usable rates - WARN_ON
Date: Wed, 08 Mar 2017 07:37:16 +0100 [thread overview]
Message-ID: <1488955036.31187.1.camel@sipsolutions.net> (raw)
In-Reply-To: <a1cd3a56-0453-7675-6895-9521a412a9cd@candelatech.com>
> > Is anyone - other than ChromeOS, which sets it just after
> > association - actually using this?
>
> I know several people who use this and depend on it being sticky.
Do you know how they use it in more detail?
> For that matter, I think LEDE and probably OpenWRT uses 'iw' quite a
> bit to affect rates.
That seems odd, but ok.
Either way, if people do rely on it being sticky then I'll do the next
best thing and just clear the mask when detecting a situation where it
would result in no usable rates, as well as rejecting it when it's
already known that it would do so.
johannes
next prev parent reply other threads:[~2017-03-08 6:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-08 0:43 rate mask resulting in no usable rates - WARN_ON Johannes Berg
2017-03-08 1:13 ` Ben Greear
2017-03-08 6:37 ` Johannes Berg [this message]
2017-03-10 15:48 ` Ben Greear
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=1488955036.31187.1.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=greearb@candelatech.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 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).