From: Adrian Bunk <bunk@stusta.de>
To: Greg KH <greg@kroah.com>
Cc: Theodore Tso <tytso@mit.edu>, Matt Mackall <mpm@selenic.com>,
Johannes Berg <johannes@sipsolutions.net>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
yi.zhu@intel.com, jketreno@linux.intel.com,
linux-wireless <linux-wireless@vger.kernel.org>,
akpm@osdl.org
Subject: [2.6.21 patch] unconditionally enable SYSFS_DEPRECATED
Date: Tue, 6 Mar 2007 00:40:52 +0100 [thread overview]
Message-ID: <20070305234052.GR3441@stusta.de> (raw)
In-Reply-To: <20070305185813.GA31465@kroah.com>
On Mon, Mar 05, 2007 at 10:58:13AM -0800, Greg KH wrote:
>
> Ok, how about the following patch. Is it acceptable to everyone?
>
> thanks,
>
> greg k-h
>
> ---
> init/Kconfig | 13 +++++++++++--
> 1 file changed, 11 insertions(+), 2 deletions(-)
>
> --- gregkh-2.6.orig/init/Kconfig
> +++ gregkh-2.6/init/Kconfig
> @@ -290,8 +290,17 @@ config SYSFS_DEPRECATED
> that belong to a class, back into the /sys/class heirachy, in
> order to support older versions of udev.
>
> - If you are using a distro that was released in 2006 or later,
> - it should be safe to say N here.
> + If you are using an OpenSuSE, Gentoo, Ubuntu, or Fedora
> + release from 2007 or later, it should be safe to say N here.
> +
> + If you are using Debian or other distros that are slow to
> + update HAL, please say Y here.
>...
The sane solution seems to be to enable SYSFS_DEPRECATED unconditionally
for all users, and schedule it's removal for mid-2008 (or later).
12 months after the first _release_ of a HAL that can live without seems
to be the first time when we can consider getting rid of it, since all
distributions with at least one release a year should ship it by then.
Currently, SYSFS_DEPRECATED is only a trap for users.
Suggested patch below.
cu
Adrian
<-- snip -->
unconditionally enable SYSFS_DEPRECATED
This patch unconditionally enables SYSFS_DEPRECATED and schedules it's
removal for July 2008.
Currently, SYSFS_DEPRECATED is only a trap for users accidentally
disabling it.
In July 2008, all distributions with at least one release a year should
be able to run without SYSFS_DEPRECATED.
Signed-off-by: Adrian Bunk <bunk@stusta.de>
diff --git a/Documentation/feature-removal-schedule.txt b/Documentation/feature-removal-schedule.txt
index c3b1430..b0bce93 100644
--- a/Documentation/feature-removal-schedule.txt
+++ b/Documentation/feature-removal-schedule.txt
@@ -316,3 +316,13 @@ Why: The option/code is
Who: Johannes Berg <johannes@sipsolutions.net>
---------------------------
+
+What: deprecated sysfs files (CONFIG_SYSFS_DEPRECATED)
+When: July 2008
+Why: None of these features or values should be used any longer,
+ as they export driver core implementation details to userspace
+ or export properties which can't be kept stable across kernel
+ releases.
+Who: Greg KH <greg@kroah.com>
+
+---------------------------
diff --git a/init/Kconfig b/init/Kconfig
index f977086..f652b6f 100644
--- a/init/Kconfig
+++ b/init/Kconfig
@@ -274,24 +274,9 @@ config CPUSETS
Say N if unsure.
config SYSFS_DEPRECATED
- bool "Create deprecated sysfs files"
+ bool
default y
help
- This option creates deprecated symlinks such as the
- "device"-link, the <subsystem>:<name>-link, and the
- "bus"-link. It may also add deprecated key in the
- uevent environment.
- None of these features or values should be used today, as
- they export driver core implementation details to userspace
- or export properties which can't be kept stable across kernel
- releases.
-
- If enabled, this option will also move any device structures
- that belong to a class, back into the /sys/class heirachy, in
- order to support older versions of udev.
-
- If you are using a distro that was released in 2006 or later,
- it should be safe to say N here.
config RELAY
bool "Kernel->user space relay support (formerly relayfs)"
next prev parent reply other threads:[~2007-03-05 23:40 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070304220857.GH23311@waste.org>
2007-03-04 23:39 ` Recent wireless breakage (ipw2200, iwconfig, NetworkManager) Johannes Berg
2007-03-05 0:25 ` Matt Mackall
2007-03-05 0:45 ` Andrew Morton
2007-03-05 1:05 ` Adrian Bunk
2007-03-05 0:46 ` Ian McDonald
2007-03-05 1:17 ` Greg KH
2007-03-05 11:20 ` Johannes Berg
2007-03-05 12:59 ` Theodore Tso
2007-03-05 18:58 ` Greg KH
2007-03-05 19:55 ` Matt Mackall
2007-03-05 22:39 ` Greg KH
2007-03-06 3:07 ` Matthew Garrett
2007-03-05 23:05 ` Jeffrey Hundstad
2007-03-05 23:40 ` Adrian Bunk [this message]
2007-03-06 0:07 ` [2.6.21 patch] unconditionally enable SYSFS_DEPRECATED Greg KH
2007-03-06 0:35 ` Adrian Bunk
2007-03-06 0:41 ` Greg KH
2007-03-06 1:30 ` Matt Mackall
2007-03-06 1:56 ` Greg KH
2007-03-06 13:20 ` Johannes Berg
2007-03-06 15:55 ` Dan Williams
2007-03-06 2:48 ` Greg KH
2007-03-06 3:04 ` Matt Mackall
2007-03-06 3:39 ` Matt Mackall
2007-03-06 4:03 ` Greg KH
2007-03-06 6:10 ` Matt Mackall
2007-03-06 19:01 ` Greg KH
2007-03-06 20:05 ` Greg KH
2007-03-06 0:35 ` Recent wireless breakage (ipw2200, iwconfig, NetworkManager) 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=20070305234052.GR3441@stusta.de \
--to=bunk@stusta.de \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=jketreno@linux.intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=netdev@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=yi.zhu@intel.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).