On Wed, Jan 16, 2013 at 06:54:16PM -0800, Kees Cook wrote: > The CONFIG_EXPERIMENTAL config item has not carried much meaning for a > while now and is almost always enabled by default. As agreed during the > Linux kernel summit, remove it from any "depends on" lines in Kconfigs. > > CC: Andrew Morton <[email protected]> > CC: "Paul E. McKenney" <[email protected]> > CC: Dmitry Kasatkin <[email protected]> > CC: James Morris <[email protected]> > CC: "Michael S. Tsirkin" <[email protected]> > CC: Akinobu Mita <[email protected]> > CC: Ingo Molnar <[email protected]> > Cc: Greg Kroah-Hartman <[email protected]> > Signed-off-by: Kees Cook <[email protected]> > Acked-by: Catalin Marinas <[email protected]>
Acked-by: Paul E. McKenney <[email protected]> > --- > lib/Kconfig | 2 +- > lib/Kconfig.debug | 2 +- > lib/Kconfig.kgdb | 2 +- > 3 files changed, 3 insertions(+), 3 deletions(-) > > diff --git a/lib/Kconfig b/lib/Kconfig > index 75cdb77..3958dc4 100644 > --- a/lib/Kconfig > +++ b/lib/Kconfig > @@ -322,7 +322,7 @@ config CPUMASK_OFFSTACK > > config DISABLE_OBSOLETE_CPUMASK_FUNCTIONS > bool "Disable obsolete cpumask functions" if DEBUG_PER_CPU_MAPS > - depends on EXPERIMENTAL && BROKEN > + depends on BROKEN > > config CPU_RMAP > bool > diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug > index 67604e5..849ecae 100644 > --- a/lib/Kconfig.debug > +++ b/lib/Kconfig.debug > @@ -455,7 +455,7 @@ config HAVE_DEBUG_KMEMLEAK > > config DEBUG_KMEMLEAK > bool "Kernel memory leak detector" > - depends on DEBUG_KERNEL && EXPERIMENTAL && HAVE_DEBUG_KMEMLEAK > + depends on DEBUG_KERNEL && HAVE_DEBUG_KMEMLEAK > select DEBUG_FS > select STACKTRACE if STACKTRACE_SUPPORT > select KALLSYMS > diff --git a/lib/Kconfig.kgdb b/lib/Kconfig.kgdb > index 43cb93f..77439eb 100644 > --- a/lib/Kconfig.kgdb > +++ b/lib/Kconfig.kgdb > @@ -5,7 +5,7 @@ config HAVE_ARCH_KGDB > menuconfig KGDB > bool "KGDB: kernel debugger" > depends on HAVE_ARCH_KGDB > - depends on DEBUG_KERNEL && EXPERIMENTAL > + depends on DEBUG_KERNEL > help > If you say Y here, it will be possible to remotely debug the > kernel using gdb. It is recommended but not required, that > -- > 1.7.9.5 > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
