From: Frederic Weisbecker <fweisbec@gmail.com>
To: Josh Triplett <josh@joshtriplett.org>
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
Sam Ravnborg <sam@ravnborg.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Make CONFIG_EXPERT select CONFIG_DEBUG_KERNEL to unhide debug options
Date: Sun, 5 Jun 2011 23:31:18 +0200 [thread overview]
Message-ID: <20110605213115.GA7862@somewhere> (raw)
In-Reply-To: <20110605210223.GA7595@leaf>
On Sun, Jun 05, 2011 at 02:02:25PM -0700, Josh Triplett wrote:
> 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>
> ---
>
> Revised as requested by Ingo Molnar.
>
> init/Kconfig | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/init/Kconfig b/init/Kconfig
> index ebafac4..5e482a3 100644
> --- a/init/Kconfig
> +++ b/init/Kconfig
> @@ -909,6 +909,7 @@ config ANON_INODES
>
> menuconfig EXPERT
> bool "Configure standard kernel features (expert users)"
> + select DEBUG_KERNEL
Please add a quick comment that explains the reason for that select. Because
without that changelog, it's very non obvious.
Thanks.
> help
> This option allows certain base kernel options and settings
> to be disabled or tweaked. This is for specialized
> --
> 1.7.5.3
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2011-06-05 21:31 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 [this message]
2011-06-06 1:23 ` [PATCHv2] " Josh Triplett
2011-06-06 22:06 ` [tip:core/debug] debug: " tip-bot for Josh Triplett
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=20110605213115.GA7862@somewhere \
--to=fweisbec@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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).