From: Johannes Berg <johannes@sipsolutions.net>
To: "Richard Schütz" <rschuetz@uni-koblenz.de>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/2] wireless: set correct mandatory rate flags
Date: Fri, 08 Sep 2017 10:57:03 +0200 [thread overview]
Message-ID: <1504861023.6177.14.camel@sipsolutions.net> (raw)
In-Reply-To: <85930e91-2c1e-53a6-5b65-d796116295fa@uni-koblenz.de>
On Fri, 2017-09-08 at 10:43 +0200, Richard Schütz wrote:
> > Hmm, I guess technically you're correct, since 11b added what's now
> > Clause 16 (was Clause 18 at the time), and that has all of them
> > mandatory? But perhaps this was actually intended for Clause 15
> > compatibility?
>
> Compatibility in what way?
Well, realistically there are only three users of this information:
* ieee80211_mandatory_rates(), used for supported station rates if we
don't know anything better in IBSS (and OCB) and for basic rates in
mesh;
* basic rates in IBSS (__cfg80211_join_ibss);
* duration calculation in ieee80211_duration, but that's just a
fallback
So I guess it's now pretty unlikely that anyone would have a pre-11b
device, so it would make sense to actually make this change.
johannes
next prev parent reply other threads:[~2017-09-08 8:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-07 15:47 [PATCH 1/2] wireless: set correct mandatory rate flags Richard Schütz
2017-09-07 15:47 ` [PATCH 2/2] wireless: return correct mandatory rates Richard Schütz
2017-09-08 6:55 ` Johannes Berg
2017-09-08 8:43 ` Richard Schütz
2017-09-08 8:53 ` Richard Schütz
2017-09-08 9:33 ` Simon Wunderlich
2017-09-08 9:03 ` Johannes Berg
2017-09-08 10:10 ` Richard Schütz
2017-09-08 10:12 ` Johannes Berg
2017-09-08 16:07 ` [PATCH v2 " Richard Schütz
2017-09-21 13:52 ` Johannes Berg
2017-09-22 10:09 ` Richard Schütz
2017-09-22 10:28 ` Johannes Berg
2017-09-08 6:54 ` [PATCH 1/2] wireless: set correct mandatory rate flags Johannes Berg
2017-09-08 8:43 ` Richard Schütz
2017-09-08 8:57 ` Johannes Berg [this message]
2017-09-21 13:49 ` Johannes Berg
2018-01-26 22:17 ` Matthias Schiffer
2018-01-30 7:43 ` Johannes Berg
2018-01-30 10:47 ` Matthias Schiffer
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=1504861023.6177.14.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=rschuetz@uni-koblenz.de \
/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.