From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: lkml <linux-kernel@vger.kernel.org>
Cc: jengelh@linux01.gwdg.de, akpm <akpm@osdl.org>
Subject: [PATCH] menu: relocate DOUBLEFAULT option
Date: Sun, 22 Jan 2006 21:23:01 -0800 [thread overview]
Message-ID: <20060122212301.3c9f6136.rdunlap@xenotime.net> (raw)
In-Reply-To: <20060122210524.2f25d0e5.rdunlap@xenotime.net>
From: Randy Dunlap <rdunlap@xenotime.net>
Move the DOUBLEFAULT option from the top-level menu to the
EMBEDDED menu. Only applicable to X86_32.
Signed-off-by: Randy Dunlap <rdunlap@xenotime.net>
---
arch/i386/Kconfig | 9 ---------
init/Kconfig | 9 +++++++++
2 files changed, 9 insertions(+), 9 deletions(-)
--- linux-2616-rc1g4.orig/arch/i386/Kconfig
+++ linux-2616-rc1g4/arch/i386/Kconfig
@@ -47,15 +47,6 @@ config DMI
source "init/Kconfig"
-config DOUBLEFAULT
- default y
- bool "Enable doublefault exception handler" if EMBEDDED
- help
- This option allows trapping of rare doublefault exceptions that
- would otherwise cause a system to silently reboot. Disabling this
- option saves about 4k and might cause you much additional grey
- hair.
-
menu "Processor type and features"
choice
--- linux-2616-rc1g4.orig/init/Kconfig
+++ linux-2616-rc1g4/init/Kconfig
@@ -412,6 +412,15 @@ config SLAB
SLOB is more space efficient but does not scale well and is
more susceptible to fragmentation.
+config DOUBLEFAULT
+ default y
+ bool "Enable doublefault exception handler" if EMBEDDED && X86_32
+ help
+ This option allows trapping of rare doublefault exceptions that
+ would otherwise cause a system to silently reboot. Disabling this
+ option saves about 4k and might cause you much additional grey
+ hair.
+
endmenu # General setup
config TINY_SHMEM
---
next prev parent reply other threads:[~2006-01-23 5:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-18 20:20 menuconfig elements unaligned Jan Engelhardt
2006-01-18 20:37 ` Sam Ravnborg
2006-01-23 5:05 ` Randy.Dunlap
2006-01-23 5:23 ` Randy.Dunlap [this message]
2006-01-23 5:57 ` Sam Ravnborg
2006-01-25 13:54 ` Jan Engelhardt
2006-01-25 18:25 ` Jean Delvare
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060122212301.3c9f6136.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=akpm@osdl.org \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®