X-Git-Url: http://git.onelab.eu/?a=blobdiff_plain;f=arch%2Fmips%2FKconfig.debug;fp=arch%2Fmips%2FKconfig.debug;h=d3c5cc3b9c9dc80d7d5fdeb172d2342217bd68fb;hb=64ba3f394c830ec48a1c31b53dcae312c56f1604;hp=5d6afb52d904aecd6b618c86f42be901897cb7b3;hpb=be1e6109ac94a859551f8e1774eb9a8469fe055c;p=linux-2.6.git

diff --git a/arch/mips/Kconfig.debug b/arch/mips/Kconfig.debug
index 5d6afb52d..d3c5cc3b9 100644
--- a/arch/mips/Kconfig.debug
+++ b/arch/mips/Kconfig.debug
@@ -1,22 +1,12 @@
 menu "Kernel hacking"
 
-config TRACE_IRQFLAGS_SUPPORT
-	bool
-	default y
-
 source "lib/Kconfig.debug"
 
 config CROSSCOMPILE
 	bool "Are you using a crosscompiler"
 	help
 	  Say Y here if you are compiling the kernel on a different
-	  architecture than the one it is intended to run on.  This is just a
-	  convenience option which will select the appropriate value for
-	  the CROSS_COMPILE make variable which otherwise has to be passed on
-	  the command line from mips-linux-, mipsel-linux-, mips64-linux- and
-	  mips64el-linux- as appropriate for a particular kernel configuration.
-	  You will have to pass the value for CROSS_COMPILE manually if the
-	  name prefix for your tools is different.
+	  architecture than the one it is intended to run on.
 
 config CMDLINE
 	string "Default kernel command string"