From: Adrian Bunk Do not allow people to create configurations with CONFIG_BROKEN=y. The sole reason for CONFIG_BROKEN=y would be if you are working on fixing a broken driver, but in this case editing the Kconfig file is trivial. Never ever should a user enable CONFIG_BROKEN. Signed-off-by: Adrian Bunk Signed-off-by: Andrew Morton --- init/Kconfig | 11 ----------- 1 files changed, 11 deletions(-) diff -puN init/Kconfig~dont-allow-users-to-set-config_broken=y init/Kconfig --- devel/init/Kconfig~dont-allow-users-to-set-config_broken=y 2006-01-18 20:39:00.000000000 -0800 +++ devel-akpm/init/Kconfig 2006-01-18 20:39:00.000000000 -0800 @@ -31,19 +31,8 @@ config EXPERIMENTAL you say Y here, you will be offered the choice of using features or drivers that are currently considered to be in the alpha-test phase. -config CLEAN_COMPILE - bool "Select only drivers expected to compile cleanly" if EXPERIMENTAL - default y - help - Select this option if you don't even want to see the option - to configure known-broken drivers. - - If unsure, say Y - config BROKEN bool - depends on !CLEAN_COMPILE - default y config BROKEN_ON_SMP bool _