From: "Steinar H. Gunderson" <sgunderson@bigfoot.com>
To: linux-wireless@vger.kernel.org
Subject: Re: [PATCH v5 2/2] mac80211: support DTPC IE (from Cisco Client eXtensions)
Date: Wed, 3 Sep 2014 15:33:28 +0200 [thread overview]
Message-ID: <20140903133328.GC18933@sesse.net> (raw)
In-Reply-To: <1409745636.911.13.camel@jlt4.sipsolutions.net>
On Wed, Sep 03, 2014 at 02:00:36PM +0200, Johannes Berg wrote:
> I think for some vendors shipping our stack this might become
> problematic. I think it would make sense to have a Kconfig option for
> this, probably hidden away under "if EXPERT" and defaulting to yes, to
> enable this code, it might be something that interferes with more CCX
> implementations maybe?
Are there any CCX implementations for Linux at this time? Could you even do
that from just userspace? (I sort of doubt it, but it's never easy to know
what illustrious userspace programmers can do :-) )
I can make a config option, but it seems a bit odd, maybe. Are you thinking
there would be problems since this is an undocumented protocol, or because of
the possible conflict?
>> +static bool ieee80211_find_cisco_dtpc(struct ieee80211_sub_if_data
>> *sdata,
> The return value is useless here, so it could be void?
It is useless indeed; I kept it this way for symmetry with the other _find_
function and because it makes for slightly easier code around (you can set
has_cisco_pwr = directly without needing an additional statement to make it
true). But I've changed it so it's void.
I could also change it to use a return instead of an output parameter for
pwr_level_cisco if you want, but I think it might become a bit confusing to
have two so similar functions with different calling style.
>> + if (pos[0] != 0x00 || pos[1] != 0x40 ||
>> + pos[2] != 0x96 || pos[3] != 0x00) {
>> + break;
>> + }
> Please remove those useless braces - maybe run ./scripts/checkpatch.pl?
Removed. But I've already run checkpatch and it didn't complain about this
(the patch set is checkpatch-clean).
I'm in a hotel room in Seattle right now whose Wi-Fi is not Cisco-based,
so I can't test the new version as thoroughly as I'd like, but I'll at least
give it a boot test and then send an updated patch series as reply to this
message.
/* Steinar */
--
Homepage: http://www.sesse.net/
next prev parent reply other threads:[~2014-09-03 13:33 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-23 21:28 [PATCH] Support Cisco DTPC IE to reduce transmit power Steinar H. Gunderson
2014-08-24 10:37 ` Steinar H. Gunderson
2014-08-24 10:08 ` [PATCH] Support DTPC IE (from Cisco Client eXtensions) Steinar H. Gunderson
2014-08-28 7:43 ` Johannes Berg
2014-08-28 8:37 ` Steinar H. Gunderson
2014-08-29 8:19 ` Steinar H. Gunderson
2014-08-29 17:27 ` [PATCH 1/2] mac80211: split 802.11h parsing from transmit power policy Steinar H. Gunderson
2014-08-29 17:38 ` [PATCH 2/2] mac80211: support DTPC IE (from Cisco Client eXtensions) Steinar H. Gunderson
2014-08-30 0:24 ` [PATCH] Support " Steinar H. Gunderson
2014-08-30 18:45 ` Steinar H. Gunderson
2014-08-29 17:27 ` [PATCH v5 1/2] mac80211: split 802.11h parsing from transmit power policy Steinar H. Gunderson
2014-09-03 11:56 ` Johannes Berg
2014-09-03 13:21 ` Steinar H. Gunderson
2014-08-29 17:27 ` [PATCH " Steinar H. Gunderson
2014-08-29 17:38 ` [PATCH v5 2/2] mac80211: support DTPC IE (from Cisco Client eXtensions) Steinar H. Gunderson
2014-09-03 12:00 ` Johannes Berg
2014-09-03 13:33 ` Steinar H. Gunderson [this message]
2014-09-03 13:22 ` [PATCH v6 1/2] mac80211: split 802.11h parsing from transmit power policy Steinar H. Gunderson
2014-09-03 13:48 ` [PATCH v6 2/2] mac80211: support DTPC IE (from Cisco Client eXtensions) Steinar H. Gunderson
2014-09-08 8:53 ` Johannes Berg
2014-09-16 23:47 ` Steinar H. Gunderson
2014-10-06 14:52 ` Johannes Berg
2014-10-06 14:54 ` Steinar H. Gunderson
2014-09-03 19:12 ` [PATCH v5 " Johannes Berg
2014-09-07 17:02 ` Steinar H. Gunderson
2014-08-29 17:38 ` [PATCH " Steinar H. Gunderson
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=20140903133328.GC18933@sesse.net \
--to=sgunderson@bigfoot.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).