[2.6 patch] cleanup default value of SCHED_SMT

[Jean-Luc Léger]

Default values for boolean and tristate options can only be 'y', 'm' or 'n'.
This patch removes wrong default for SCHED_SMT.

Signed-off-by: Jean-Luc Léger <jean-luc.leger@xxxxxxxxxxxxxxxx>

Index: linux-2.6.17-rc1/arch/i386/Kconfig
===================================================================
--- linux-2.6.17-rc1/arch/i386/Kconfig.old      2006-04-15 22:13:19.000000000 +0200
+++ linux-2.6.17-rc1/arch/i386/Kconfig  2006-04-15 22:14:14.000000000 +0200
@@ -224,7 +224,6 @@
 config SCHED_SMT
 	bool "SMT (Hyperthreading) scheduler support"
 	depends on SMP
-	default off
 	help
 	  SMT scheduler support improves the CPU scheduler's decision making
 	  when dealing with Intel Pentium 4 chips with HyperThreading at a
Index: linux-2.6.17-rc1/arch/ia64/Kconfig
===================================================================
--- linux-2.6.17-rc1/arch/ia64/Kconfig.old      2006-04-15 22:12:11.000000000 +0200
+++ linux-2.6.17-rc1/arch/ia64/Kconfig  2006-04-15 22:13:05.000000000 +0200
@@ -282,7 +282,6 @@
 config SCHED_SMT
 	bool "SMT scheduler support"
 	depends on SMP
-	default off
 	help
 	  Improves the CPU scheduler's decision making when dealing with
 	  Intel IA64 chips with MultiThreading at a cost of slightly increased
Index: linux-2.6.17-rc1/arch/powerpc/Kconfig
===================================================================
--- linux-2.6.17-rc1/arch/powerpc/Kconfig.old   2006-04-15 22:10:10.000000000 +0200
+++ linux-2.6.17-rc1/arch/powerpc/Kconfig       2006-04-15 22:12:00.000000000 +0200
@@ -688,7 +688,6 @@
 config SCHED_SMT
 	bool "SMT (Hyperthreading) scheduler support"
 	depends on PPC64 && SMP
-	default off
 	help
 	  SMT scheduler support improves the CPU scheduler's decision making
 	  when dealing with POWER5 cpus at a cost of slightly increased


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/