From: Johannes Berg <johannes@sipsolutions.net>
To: Ben Greear <greearb@candelatech.com>, linux-wireless@vger.kernel.org
Subject: Re: [PATCH-v2 1/2] mac80211: Take bitrates into account when building IEs.
Date: Tue, 15 Mar 2016 21:20:24 +0100 [thread overview]
Message-ID: <1458073224.2871.22.camel@sipsolutions.net> (raw)
In-Reply-To: <56E833FE.1080904@candelatech.com>
On Tue, 2016-03-15 at 09:10 -0700, Ben Greear wrote:
>
> The logic I wrote is basically exactly this. It uses the configured
> rates to specify which of the hardware's rates are allowed and
> disabled.
>
I understand that. I just take issue with the fact that we have to
sprinkle "magic pixie dust" (in form of the override function calls)
everywhere throughout the code.
johannes
next prev parent reply other threads:[~2016-03-15 20:20 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-20 17:24 [PATCH-v2 1/2] mac80211: Take bitrates into account when building IEs greearb
2015-10-20 17:24 ` [PATCH-v2 2/2] mac80211: ensure association req uses configured ratemask greearb
2016-01-26 11:18 ` Johannes Berg
2015-11-05 18:47 ` [PATCH-v2 1/2] mac80211: Take bitrates into account when building IEs Ben Greear
2015-11-05 19:04 ` Johannes Berg
2016-01-26 11:16 ` Johannes Berg
2016-01-26 15:19 ` Ben Greear
2016-02-04 9:02 ` Johannes Berg
2016-02-04 17:52 ` Ben Greear
2016-02-18 20:32 ` Johannes Berg
2016-02-18 20:40 ` Ben Greear
2016-02-18 20:45 ` Johannes Berg
2016-02-18 20:59 ` Ben Greear
2016-02-18 21:14 ` Johannes Berg
2016-02-18 21:54 ` Ben Greear
2016-02-23 11:06 ` Johannes Berg
2016-03-10 17:56 ` Ben Greear
2016-03-15 14:15 ` Johannes Berg
2016-03-15 16:10 ` Ben Greear
2016-03-15 20:20 ` Johannes Berg [this message]
2016-06-10 18:43 ` Ben Greear
2016-06-21 9:40 ` Johannes Berg
2016-06-21 14:19 ` Ben Greear
2016-03-15 14:17 ` Johannes Berg
-- strict thread matches above, loose matches on Subject: below --
2015-10-20 17:22 greearb
2015-10-20 17:26 ` 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=1458073224.2871.22.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 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.