linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: "Luis R. Rodriguez" <rodrigue@qca.qualcomm.com>
Cc: Kalle Valo <kvalo@qca.qualcomm.com>,
	Arend van Spriel <arend@broadcom.com>,
	linux-wireless@vger.kernel.org, me@bobcopeland.com,
	mickflemm@gmail.com
Subject: Re: [RFC 0/3] wireless: add CONFIG_CFG80211_EXPERT
Date: Fri, 15 Jun 2012 10:16:51 +0200	[thread overview]
Message-ID: <1339748211.4512.6.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <20120614193104.GD32257@tux>

On Thu, 2012-06-14 at 12:31 -0700, Luis R. Rodriguez wrote:

> This option should really be used by OEM/ODM that have assured proper
> certification or scientists using a shielded room. Distros should be strongly
> adviced not to use this as their users tend to be unaware or the distribution
> ODM / OEM may not have done the necessary work to ensure proper regulatory
> certification. Perhaps we can clarify that there is a heavier onus on
> regulatory certification if these options are enabled. Linux distributions may
> be eager to please their users, but I would expect them to have common sense as
> well. We would just have to educate them about this option.

Yet nothing in the name of the option says so... You vaguely described
it in the Kconfig help text but that text feels like weaselling your way
out :-)

> As for a name, I thought about it for a while and given that we have different
> "wireless" technologies -- bluetooth, NFC, naming this CONFIG_WIRELESS_EXPERT
> seemed odd, and given that our 802.11 framework is under cfg80211 naming it
> CONFIG_CFG80211_EXPERT seemed appropriate. But even if its under cfg80211
> perhaps something more explicit about the implications may be better, how
> about CONFIG_CFG80211_MAY_BREAK_CERTIFICATION ?

Or you could just be explicit about it and call it
CONFIG_WIRELESS_REGULATORY_BREAKAGE or something like that :-)

johannes


  reply	other threads:[~2012-06-15  8:16 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-09  0:51 [RFC 0/3] wireless: add CONFIG_CFG80211_EXPERT Luis R. Rodriguez
2012-06-09  0:51 ` [RFC 1/3] cfg80211: " Luis R. Rodriguez
2012-06-09  0:51 ` [RFC 2/3] ath5k: replace modparam_all_channels with CONFIG_ATH5K_TEST_CHANNELS Luis R. Rodriguez
2012-06-09  0:51 ` [RFC 3/3] ath9k: make CONFIG_ATH9K_DFS_CERTIFIED depend on CONFIG_CFG80211_EXPERT Luis R. Rodriguez
2012-06-09  7:55 ` [RFC 0/3] wireless: add CONFIG_CFG80211_EXPERT Johannes Berg
2012-06-09 19:51   ` Arend van Spriel
2012-06-11  7:32     ` Johannes Berg
2012-06-11 14:40       ` Kalle Valo
2012-06-11 14:45         ` Johannes Berg
2012-06-11 15:46           ` Kalle Valo
2012-06-14 19:31           ` Luis R. Rodriguez
2012-06-15  8:16             ` Johannes Berg [this message]
2012-06-15  8:21               ` Kalle Valo
2012-06-15 11:06                 ` Arend van Spriel
2012-06-15 16:09                   ` Kalle Valo
2012-06-15 16:53                     ` Luis R. Rodriguez
2012-06-16 12:13                       ` Arend van Spriel
2012-06-18 15:37                         ` Luis R. Rodriguez

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=1339748211.4512.6.camel@jlt3.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=arend@broadcom.com \
    --cc=kvalo@qca.qualcomm.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=me@bobcopeland.com \
    --cc=mickflemm@gmail.com \
    --cc=rodrigue@qca.qualcomm.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).