From: "Luis R. Rodriguez" <rodrigue@qca.qualcomm.com>
To: Arend van Spriel <arend@broadcom.com>
Cc: Kalle Valo <kvalo@qca.qualcomm.com>,
Johannes Berg <johannes@sipsolutions.net>,
<linux-wireless@vger.kernel.org>, <me@bobcopeland.com>,
<mickflemm@gmail.com>
Subject: Re: [RFC 0/3] wireless: add CONFIG_CFG80211_EXPERT
Date: Mon, 18 Jun 2012 08:37:42 -0700 [thread overview]
Message-ID: <20120618153742.GB12526@tux> (raw)
In-Reply-To: <4FDC7887.8090907@broadcom.com>
On Sat, Jun 16, 2012 at 02:13:59PM +0200, Arend van Spriel wrote:
> On 06/15/2012 06:53 PM, Luis R. Rodriguez wrote:
> > So how about CONFIG_CFG80211_CERTIFICATION_ONUS which can be defined
> > as an option for features / options whereby the onus for regulatory
> > certification is being accepted by the option enabler? Pretty simple
> > and to the point, and would allow for research code but also code
> > whereby a bit more work is required on the enabler like DFS
> > certification.
>
> English is not my native language so I had to look up the meaning of the
> word 'onus'. I guess I am fine with it.
Great, I'll respin.
> Apart from the naming I addressed that if would be better to have it
> device on CONFIG_WLAN instead of CFG80211 as it will be used to enable
> 802.11 device driver features. Any thoughts on that?
OK so we have CONFIG_WLAN for devices and CONFIG_WIRELESS for the subsystem
which is enabled if anyone enables CONFIG_WLAN. The kconfig entry will not only
be used for 802.11 device drivers, it will also be used for some generic
subsystem options, I'll send patches for an idea there later after the first
slew go in.
Luis
prev parent reply other threads:[~2012-06-18 15:38 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
2012-06-15 16:53 ` Luis R. Rodriguez
2012-06-16 12:13 ` Arend van Spriel
2012-06-18 15:37 ` Luis R. Rodriguez [this message]
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=20120618153742.GB12526@tux \
--to=rodrigue@qca.qualcomm.com \
--cc=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 \
/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).