From: Kyle McMartin <kyle@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: mingo@redhat.com
Subject: [PATCH] CONFIG_PANIC_ON_OOPS should be shown if DEBUG_KERNEL
Date: Tue, 22 Jan 2013 14:21:03 -0500 [thread overview]
Message-ID: <20130122192102.GE6538@redacted.bos.redhat.com> (raw)
CONFIG_EXPERT is a bit silly a place for this, and hides it
unnecessarily. CONFIG_DEBUG_KERNEL makes much more sense.
Signed-off-by: Kyle McMartin <kyle@redhat.com>
--- a/lib/Kconfig.debug
+++ b/lib/Kconfig.debug
@@ -243,7 +243,7 @@ config BOOTPARAM_SOFTLOCKUP_PANIC_VALUE
default 1 if BOOTPARAM_SOFTLOCKUP_PANIC
config PANIC_ON_OOPS
- bool "Panic on Oops" if EXPERT
+ bool "Panic on Oops" if DEBUG_KERNEL
default n
help
Say Y here to enable the kernel to panic when it oopses. This
next reply other threads:[~2013-01-22 19:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-22 19:21 Kyle McMartin [this message]
2013-01-23 22:04 ` [PATCH] CONFIG_PANIC_ON_OOPS should be shown if DEBUG_KERNEL Andrew Morton
2013-01-24 10:18 ` Ingo Molnar
2013-01-24 19:43 ` [PATCH] unhide CONFIG_PANIC_ON_OOPS Kyle McMartin
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=20130122192102.GE6538@redacted.bos.redhat.com \
--to=kyle@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).