From: "Arend van Spriel" <arend@broadcom.com>
To: "Johannes Berg" <johannes@sipsolutions.net>
Cc: "Luis R. Rodriguez" <rodrigue@qca.qualcomm.com>,
linux-wireless@vger.kernel.org, me@bobcopeland.com,
mickflemm@gmail.com, kvalo@qca.qualcomm.com
Subject: Re: [RFC 0/3] wireless: add CONFIG_CFG80211_EXPERT
Date: Sat, 9 Jun 2012 21:51:18 +0200 [thread overview]
Message-ID: <4FD3A936.8070600@broadcom.com> (raw)
In-Reply-To: <1339228530.4539.0.camel@jlt3.sipsolutions.net>
On 06/09/2012 09:55 AM, Johannes Berg wrote:
> On Fri, 2012-06-08 at 17:51 -0700, Luis R. Rodriguez wrote:
>> From: "Luis R. Rodriguez" <mcgrof@qca.qualcomm.com>
>>
>> Turns out that standard Linux distributions leave CONFIG_EXPERT
>> enabled. This makes this option useless for wireless testing / research
>> purposes as we don't want certain features enabled on all kernel
>> builds. This adds a new CONFIG_CFG80211_EXPERT and makes a few
>> features depend on them.
>
> I'm not sure I see the point in CFG80211_EXPERT. All the features you're
> putting in there have nothing to do with cfg80211 at all anyway.
My understanding of this is that CFG80211_EXPERT was chosen because
cfg80211 provides the kernel side of the regulatory framework.
Gr. AvS
next prev parent reply other threads:[~2012-06-09 19:51 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 [this message]
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
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=4FD3A936.8070600@broadcom.com \
--to=arend@broadcom.com \
--cc=johannes@sipsolutions.net \
--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 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.