Skip to contentSkip to conversation

don't allow users to set CONFIG_BROKEN=y

PATCH New Adrian Bunk 1 participant 1 message Jan 19, 2006

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 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.

---

This patch was already sent on:
- 6 Jan 2006
- 13 Dec 2005

init/Kconfig renamed from init/Kconfig.old +0 -11
@@ -31,19 +31,8 @@
 	  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