[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080305101617.GD19059@localhost.sw.ru>
Date: Wed, 5 Mar 2008 13:16:17 +0300
From: Alexey Dobriyan <adobriyan@...ru>
To: Ingo Molnar <mingo@...e.hu>
Cc: Greg KH <gregkh@...e.de>, "Zhang, Rui" <rui.zhang@...el.com>,
linux-kernel <linux-kernel@...r.kernel.org>,
kay.sievers@...y.org, Andrew Morton <akpm@...ux-foundation.org>,
"Rafael J. Wysocki" <rjw@...k.pl>,
Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: 2.6.25-rc regression: kernel panic on boot
On Tue, Mar 04, 2008 at 02:54:47PM +0100, Ingo Molnar wrote:
> CONFIG_SYSFS_DEPRECATED=y changed its meaning recently and causes
> regressions in working setups that had SYSFS_DEPRECATED disabled.
>
> so rename it to SYSFS_DEPRECATED_V2 so that testers pick up the new
> default via 'make oldconfig', even if their old .config's disabled
> CONFIG_SYSFS_DEPRECATED ...
It has all the same help text, so people who disabled it in the past
will disable again!
> --- linux.orig/init/Kconfig
> +++ linux/init/Kconfig
> @@ -367,9 +367,13 @@ config RESOURCE_COUNTERS
> depends on CGROUPS
>
> config SYSFS_DEPRECATED
> + bool
> +
> +config SYSFS_DEPRECATED_V2
> bool "Create deprecated sysfs files"
> depends on SYSFS
> default y
> + select SYSFS_DEPRECATED
> help
> This option creates deprecated symlinks such as the
> "device"-link, the <subsystem>:<name>-link, and the
Is anyone aware of a case when turning SYSFS_DEPRECATED back on also
breaks something? I mean, option can be simply removed and sysfs people
can finally stop breaking boxes.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists