From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: "Lukáš Turek" <8an@praha12.net>
Cc: Luis Rodriguez <Luis.Rodriguez@Atheros.com>,
"johannes@sipsolutions.net" <johannes@sipsolutions.net>,
"ath5k-devel@lists.ath5k.org" <ath5k-devel@lists.ath5k.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linville@tuxdriver.com" <linville@tuxdriver.com>
Subject: Re: [ath5k-devel] [PATCH 1/5] nl80211: Add new WIPHY attribute COVERAGE_CLASS
Date: Tue, 15 Dec 2009 13:44:06 -0800 [thread overview]
Message-ID: <20091215214406.GB2067@tux> (raw)
In-Reply-To: <200912152207.33024.8an@praha12.net>
On Tue, Dec 15, 2009 at 01:07:32PM -0800, Lukáš Turek wrote:
> On 15.12.2009 20:02 you wrote:
> > And if your IBSS and the AP already sent the coverage class through the
> > country IE I am not sure if we should allow overriding it.
> Overriding the coverage class is harmless, it won't allow you to break any
> laws like overriding regulatory domain does.
I'm not concerned about how you override it, I am concerned about
creating consistancy though and avoiding tweaks through userspace
which can screw things. I'll address this in more details in the other
threads.
Luis
next prev parent reply other threads:[~2009-12-15 21:44 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-15 17:56 [PATCH 0/5] Setting coverage class (and ACK timeout and slot time), take two Lukáš Turek
2009-12-15 17:56 ` [PATCH 1/5] nl80211: Add new WIPHY attribute COVERAGE_CLASS Lukáš Turek
2009-12-15 19:00 ` [ath5k-devel] " Luis R. Rodriguez
2009-12-15 19:02 ` Luis R. Rodriguez
2009-12-15 21:07 ` Lukáš Turek
2009-12-15 21:44 ` Luis R. Rodriguez [this message]
2009-12-16 8:03 ` Holger Schurig
2009-12-15 20:56 ` Lukáš Turek
2009-12-15 21:58 ` Luis R. Rodriguez
2009-12-15 22:48 ` Felix Fietkau
2009-12-15 22:52 ` Lukáš Turek
2009-12-16 8:30 ` Luis R. Rodriguez
2009-12-18 16:33 ` Lukáš Turek
2009-12-18 17:20 ` Luis R. Rodriguez
2009-12-15 17:56 ` [PATCH 2/5] mac80211: Add new callback set_coverage_class Lukáš Turek
2009-12-15 18:07 ` Johannes Berg
2009-12-15 18:11 ` [ath5k-devel] " Luis R. Rodriguez
2009-12-15 21:23 ` Lukáš Turek
2009-12-15 21:25 ` Johannes Berg
2009-12-15 17:56 ` [PATCH 3/5] ath5k: Fix functions for getting/setting slot time Lukáš Turek
2009-12-15 17:56 ` [PATCH 4/5] ath5k: Reimplement clock rate to usec conversion Lukáš Turek
2009-12-21 10:26 ` [ath5k-devel] " 海藻敬之
2009-12-21 12:38 ` Lukáš Turek
[not found] ` <4B301FE9.2020702@thinktube.com>
2009-12-22 16:08 ` Lukáš Turek
[not found] ` <4B2F50DD.60701@thinktube.com>
2009-12-21 12:40 ` Lukáš Turek
2009-12-21 15:08 ` Bob Copeland
2009-12-21 15:28 ` Lukáš Turek
2009-12-22 3:28 ` Bob Copeland
2009-12-15 17:56 ` [PATCH 5/5] ath5k: Implement mac80211 callback set_coverage_class Lukáš Turek
2009-12-15 18:50 ` [ath5k-devel] " Luis R. Rodriguez
2009-12-15 19:01 ` Luis R. Rodriguez
2009-12-15 21:35 ` Lukáš Turek
2009-12-15 22:07 ` Luis R. Rodriguez
2009-12-15 17:56 ` [PATCH] iw: Add support for NL80211_ATTR_WIPHY_COVERAGE_CLASS Lukáš Turek
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=20091215214406.GB2067@tux \
--to=lrodriguez@atheros.com \
--cc=8an@praha12.net \
--cc=Luis.Rodriguez@Atheros.com \
--cc=ath5k-devel@lists.ath5k.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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).