linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Arend van Spriel <arend@broadcom.com>,
	"Luis R. Rodriguez" <rodrigue@qca.qualcomm.com>,
	<linux-wireless@vger.kernel.org>, <me@bobcopeland.com>,
	<mickflemm@gmail.com>
Subject: Re: [RFC 0/3] wireless: add CONFIG_CFG80211_EXPERT
Date: Mon, 11 Jun 2012 18:46:18 +0300	[thread overview]
Message-ID: <4FD612CA.1050604@qca.qualcomm.com> (raw)
In-Reply-To: <1339425944.4520.27.camel@jlt3.sipsolutions.net>

On 06/11/2012 05:45 PM, Johannes Berg wrote:
> On Mon, 2012-06-11 at 17:40 +0300, Kalle Valo wrote:
> 
>> I would compare this with NL80211_TESTMODE, we don't want distributions
>> to enable that either. Of course nothing prevents distros to enable
>> CFG80211_EXPERT but we need to be active to make sure it's not enabled
>> (ie. check the distro configs and file bugs etc).
> 
> Right, but that's actually a feature. I see little value in a pretty
> much meaningless "EXPERT wireless" Kconfig symbol that only groups
> others.

Ah, I see.

> If, as Arend suggested, it actually has some meaning, then it
> may make more sense.

Yeah, I see your point.

FWIW I do see the value with CFG80211_EXPERT as it makes more difficult
for users to accidentally enable certain features. And it makes it
easier for us to search for distros which have CFG80211_EXPERT enabled.

Kalle

  reply	other threads:[~2012-06-11 15:46 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 [this message]
2012-06-14 19:31           ` Luis R. Rodriguez
2012-06-15  8:16             ` Johannes Berg
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=4FD612CA.1050604@qca.qualcomm.com \
    --to=kvalo@qca.qualcomm.com \
    --cc=arend@broadcom.com \
    --cc=johannes@sipsolutions.net \
    --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).