From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Arend van Spriel <arend@broadcom.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
"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: Fri, 15 Jun 2012 19:09:54 +0300 [thread overview]
Message-ID: <4FDB5E52.1020608@qca.qualcomm.com> (raw)
In-Reply-To: <4FDB1740.60707@broadcom.com>
On 06/15/2012 02:06 PM, Arend van Spriel wrote:
> On 06/15/2012 10:21 AM, Kalle Valo wrote:
>> On 06/15/2012 11:16 AM, Johannes Berg wrote:
>>>> 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 :-)
>>
>> CONFIG_WIRELESS_CERTIFIED?
>
> That one looks familiar ;-)
Sorry, did you suggest that already? I missed that. I guess I need to
start organising my email better :)
Kalle
next prev parent reply other threads:[~2012-06-15 16:10 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
2012-06-15 8:21 ` Kalle Valo
2012-06-15 11:06 ` Arend van Spriel
2012-06-15 16:09 ` Kalle Valo [this message]
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=4FDB5E52.1020608@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 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.