From: Randy Dunlap <randy.dunlap@oracle.com>
To: James Ketrenos <jketreno@linux.intel.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [PATCH] d80211: create net/wireless/Kconfig and make nl80211 optional
Date: Fri, 23 Feb 2007 13:55:39 -0800 [thread overview]
Message-ID: <20070223135539.8a4fdff6.randy.dunlap@oracle.com> (raw)
In-Reply-To: <45DF60F9.9090806@linux.intel.com>
On Fri, 23 Feb 2007 13:47:37 -0800 James Ketrenos wrote:
> Ok... this time for sure. Maybe :) At least its Friday.
almost ....
> James
>
> ----
>
> [PATCH] create net/wireless/Kconfig and make nl80211 optional
>
> ---
> net/Kconfig | 17 +----------------
> net/wireless/Kconfig | 33 +++++++++++++++++++++++++++++++++
> net/wireless/Makefile | 3 ++-
> net/wireless/nl80211.h | 10 ++++++++++
> 4 files changed, 46 insertions(+), 17 deletions(-)
> ---
> diff --git a/net/Kconfig b/net/Kconfig
> index 3bff36e..6fa4d68 100644
> --- a/net/Kconfig
> +++ b/net/Kconfig
> @@ -228,22 +228,7 @@ config WIRELESS_EXT
> config FIB_RULES
> bool
>
> -config CFG80211
> - tristate "Improved wireless configuration API"
> -
> -config CFG80211_WEXT_COMPAT
> - bool "cfg80211 Wireless Extensions compatibility"
> - depends CFG80211
> - default y
> - ---help---
> - This option allows using devices whose drivers have been
> - converted to use the new cfg80211 with wireless extensions,
> - providing WE-20 compatibility. Note that cfg80211's "native"
> - interface is nl80211 using generic netlink. The wireless
> - extensions are being deprecated, but userspace tools may still
> - be using them.
> -
> - If unsure, say Y.
> +source "net/wireless/Kconfig"
>
> endif # if NET
> endmenu # Networking
> diff --git a/net/wireless/Kconfig b/net/wireless/Kconfig
> new file mode 100644
> index 0000000..7e83504
> --- /dev/null
> +++ b/net/wireless/Kconfig
> @@ -0,0 +1,33 @@
> +config CFG80211
> + tristate "Improved wireless configuration API"
> +
> +config CFG80211_WEXT_COMPAT
> + bool "cfg80211 Wireless Extensions compatibility"
> + depends CFG80211
> + default y
> + ---help---
> + This option allows using devices whose drivers have been
> + converted to use the new cfg80211 with wireless extensions,
> + providing WE-20 compatibility.
> +
> + Note that cfg80211's "native" interface is nl80211 using
> + generic netlink. The wireless extensions are being
> + deprecated, but userspace tools may still be using them.
> +
> + If unsure, say Y.
All of the text under ---help--- should be (should have been :) indented
2 spaces... (yes, I know it wasn't before, but should have been).
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2007-02-23 22:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-23 20:41 [PATCH] d80211: create net/wireless/Kconfig and make nl80211 optional James Ketrenos
2007-02-23 20:52 ` Johannes Berg
2007-02-23 21:01 ` James Ketrenos
2007-02-23 21:47 ` James Ketrenos
2007-02-23 21:55 ` Randy Dunlap [this message]
2007-02-23 22:11 ` Johannes Berg
2007-02-23 22:52 ` James Ketrenos
2007-02-23 20:56 ` James Ketrenos
2007-02-23 21:02 ` Johannes Berg
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=20070223135539.8a4fdff6.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=jketreno@linux.intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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