[PATCH] don't allow users to set CONFIG_BROKEN=y
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 <bunk@stusta.de> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
This commit is contained in:
parent
145046d31e
commit
3636641bb2
1 changed files with 0 additions and 11 deletions
11
init/Kconfig
11
init/Kconfig
|
@ -31,19 +31,8 @@ config EXPERIMENTAL
|
||||||
you say Y here, you will be offered the choice of using features or
|
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.
|
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
|
config BROKEN
|
||||||
bool
|
bool
|
||||||
depends on !CLEAN_COMPILE
|
|
||||||
default y
|
|
||||||
|
|
||||||
config BROKEN_ON_SMP
|
config BROKEN_ON_SMP
|
||||||
bool
|
bool
|
||||||
|
|
Loading…
Reference in a new issue