From: Johannes Berg <johannes@sipsolutions.net>
To: Adrian Bunk <bunk@kernel.org>
Cc: Pierre Ossman <drzeus-list@drzeus.cx>,
"John W. Linville" <linville@tuxdriver.com>,
Jean Tourrilhes <jt@hpl.hp.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC: 2.6 patch] clarify the WIRELESS_EXT_SYSFS help text
Date: Thu, 24 Jul 2008 22:21:44 +0200 [thread overview]
Message-ID: <1216930904.13587.94.camel@johannes.berg> (raw)
In-Reply-To: <20080724124225.GD32109@cs181140183.pp.htv.fi>
[-- Attachment #1: Type: text/plain, Size: 840 bytes --]
Sure, since we don't know what the next release will be there's little
point in trying to predict it, this patch is fine with me.
> Current Hal uses the CONFIG_WIRELESS_EXT_SYSFS files, so don't claim
> there were no known users and recommend to enable the option.
>
> Signed-off-by: Adrian Bunk <bunk@kernel.org>
Acked-by: Johannes Berg <johannes@sipsolutions.net>
>
> b685f62718b947264657c298e5ee5b2149200f68
> diff --git a/net/wireless/Kconfig b/net/wireless/Kconfig
> index ab015c6..e582432 100644
> --- a/net/wireless/Kconfig
> +++ b/net/wireless/Kconfig
> @@ -39,4 +39,4 @@ config WIRELESS_EXT_SYSFS
> files in /sys/class/net/*/wireless/. The same information
> is available via the ioctls as well.
>
> - Say Y if you have programs using it (we don't know of any).
> + If unsure, say Y.
>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2008-07-24 20:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-24 9:58 22bb1be4d27... breaks hal (and NM) Pierre Ossman
2008-07-24 11:38 ` Johannes Berg
2008-07-24 11:57 ` Peter Zijlstra
2008-07-24 12:08 ` Johannes Berg
2008-07-24 12:11 ` Andrew Morton
2008-07-24 12:22 ` Peter Zijlstra
2008-07-24 12:33 ` Alistair John Strachan
2008-07-24 12:42 ` [RFC: 2.6 patch] clarify the WIRELESS_EXT_SYSFS help text Adrian Bunk
2008-07-24 12:54 ` Peter Zijlstra
2008-07-24 20:21 ` Johannes Berg [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=1216930904.13587.94.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=bunk@kernel.org \
--cc=drzeus-list@drzeus.cx \
--cc=jt@hpl.hp.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®