From: tip-bot for Josh Triplett <josh@joshtriplett.org>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@redhat.com,
torvalds@linux-foundation.org, sam@ravnborg.org,
fweisbec@gmail.com, tglx@linutronix.de, josh@joshtriplett.org,
mingo@elte.hu
Subject: [tip:core/debug] debug: Make CONFIG_EXPERT select CONFIG_DEBUG_KERNEL to unhide debug options
Date: Mon, 6 Jun 2011 22:06:48 GMT [thread overview]
Message-ID: <tip-f505c553dbe24b18a8590eb0eb5890a839acd0c3@git.kernel.org> (raw)
In-Reply-To: <20110606012358.GA1909@leaf>
Commit-ID: f505c553dbe24b18a8590eb0eb5890a839acd0c3
Gitweb: http://git.kernel.org/tip/f505c553dbe24b18a8590eb0eb5890a839acd0c3
Author: Josh Triplett <josh@joshtriplett.org>
AuthorDate: Sun, 5 Jun 2011 18:23:58 -0700
Committer: Ingo Molnar <mingo@elte.hu>
CommitDate: Tue, 7 Jun 2011 00:05:15 +0200
debug: Make CONFIG_EXPERT select CONFIG_DEBUG_KERNEL to unhide debug options
Several debugging options currently default to y, such as
CONFIG_DEBUG_BUGVERBOSE and CONFIG_DEBUG_RODATA. Embedded users
might want to turn those options off to save space; however,
turning them off requires turning on CONFIG_DEBUG_KERNEL to
unhide them. Since CONFIG_DEBUG_KERNEL exists specifically to
unhide debugging options, and CONFIG_EXPERT exists specifically
to unhide options potentially needed by experts and/or embedded
users, make CONFIG_EXPERT automatically imply
CONFIG_DEBUG_KERNEL.
Signed-off-by: Josh Triplett <josh@joshtriplett.org>
Acked-by: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Sam Ravnborg <sam@ravnborg.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Link: http://lkml.kernel.org/r/20110606012358.GA1909@leaf
Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
init/Kconfig | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/init/Kconfig b/init/Kconfig
index ebafac4..14370d3 100644
--- a/init/Kconfig
+++ b/init/Kconfig
@@ -909,6 +909,8 @@ config ANON_INODES
menuconfig EXPERT
bool "Configure standard kernel features (expert users)"
+ # Unhide debug options, to make the on-by-default options visible
+ select DEBUG_KERNEL
help
This option allows certain base kernel options and settings
to be disabled or tweaked. This is for specialized
next prev parent reply other threads:[~2011-06-06 22:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-05 21:02 [PATCH] Make CONFIG_EXPERT select CONFIG_DEBUG_KERNEL to unhide debug options Josh Triplett
2011-06-05 21:31 ` Frederic Weisbecker
2011-06-06 1:23 ` [PATCHv2] " Josh Triplett
2011-06-06 22:06 ` tip-bot for Josh Triplett [this message]
2011-06-06 15:18 ` [PATCH] " Ingo Molnar
2011-06-06 16:51 ` [PATCHv3] " Josh Triplett
2011-06-06 18:16 ` Frederic Weisbecker
2011-06-06 18:39 ` Josh Triplett
2011-06-06 21:34 ` Frederic Weisbecker
2011-06-06 22:02 ` Ingo Molnar
2011-06-06 22:08 ` [PATCHv4] " Josh Triplett
2011-06-06 23:48 ` Frederic Weisbecker
2011-06-06 21:39 ` [tip:core/debug] debug: " tip-bot for Josh Triplett
2011-06-06 21:45 ` Frederic Weisbecker
2011-06-06 22:09 ` Josh Triplett
2011-06-07 10:18 ` Ingo Molnar
2011-06-07 15:34 ` Josh Triplett
2011-06-07 18:04 ` Ingo Molnar
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=tip-f505c553dbe24b18a8590eb0eb5890a839acd0c3@git.kernel.org \
--to=josh@joshtriplett.org \
--cc=fweisbec@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=sam@ravnborg.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).