From: Li Zefan <lizf@cn.fujitsu.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Randy Dunlap <randy.dunlap@oracle.com>,
Michal Marek <mmarek@suse.cz>,
linux-kbuild@vger.kernel.org, Tim Bird <tim.bird@am.sony.com>
Subject: [PATCH 0/6] kconfig: add support to show hidden options which have prompts
Date: Wed, 14 Apr 2010 11:43:25 +0800 [thread overview]
Message-ID: <4BC539DD.5040003@cn.fujitsu.com> (raw)
Usage:
(in menuconfig)
Press <Z> to show all config symbols which have prompts.
Quote Tim Bird (http://lkml.org/lkml/2010/3/19/319):
| I've been bitten by this numerous times. I most often
| use ftrace on ARM, but when I go back to x86, I almost
| always go through a sequence of searching for the
| function graph tracer in the menus, then realizing it's
| completely missing until I disable CC_OPTIMIZE_FOR_SIZE.
|
| Is there any way to have the menu item appear, but be
| unsettable unless the SIZE option is disabled? I'm
| not a Kconfig guru...
I myself found this useful too. For example, I need to test
ftrace/tracing and want to be sure all the tracing features are
enabled, so I enter the "Tracers" menu, and press <Z> to
see if there is any config hidden.
I noticed gconfig and xconfig have a button "Show all options",
but that's a bit too much, and I think normally what we are not
interested in those configs which have no prompt thus can't be
changed by users.
Exmaple:
--- Tracers
-*- Kernel Function Tracer
- - Kernel Function Graph Tracer
[*] Interrupts-off Latency Tracer
- - Preemption-off Latency Tracer
[*] Sysprof Tracer
Here you can see 2 tracers are not selectable, and then can find
out how to make them selectable.
I also add this support for gconfig, but haven't done for xconfig.
btw: are there many users using gconfig/xconfig today ?
---
Documentation/kbuild/kconfig-language.txt | 2 +-
scripts/kconfig/gconf.c | 113 ++++++++++-------------------
scripts/kconfig/gconf.glade | 26 +++++--
scripts/kconfig/lkc_proto.h | 3 +-
scripts/kconfig/lxdialog/inputbox.c | 4 +-
scripts/kconfig/lxdialog/menubox.c | 22 +++---
scripts/kconfig/mconf.c | 22 +++++-
scripts/kconfig/menu.c | 12 +++-
scripts/kconfig/zconf.tab.c_shipped | 21 +++++-
scripts/kconfig/zconf.y | 21 +++++-
10 files changed, 136 insertions(+), 110 deletions(-)
next reply other threads:[~2010-04-14 3:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-14 3:43 Li Zefan [this message]
2010-04-14 3:44 ` [PATCH 1/6] kconfig: some small fixes Li Zefan
2010-04-14 3:44 ` [PATCH 2/6] kconfig: fix zconfdump() Li Zefan
2010-04-14 3:44 ` [PATCH 3/6] gconfig: remove dbg_print_ptype() and dbg_print_stype() Li Zefan
2010-04-14 3:44 ` [PATCH 4/6] gconfig: remove show_debug option Li Zefan
2010-04-14 3:46 ` [PATCH 5/6] menuconfig: add support to show hidden options which have prompts Li Zefan
2010-04-14 23:48 ` Randy Dunlap
2010-04-15 7:31 ` Li Zefan
2010-04-15 7:54 ` Michal Marek
2010-04-15 8:02 ` Li Zefan
2010-04-14 3:46 ` [PATCH 6/6] gconfig: add support to show hidden options that " Li Zefan
2010-04-14 23:48 ` Randy Dunlap
2010-04-15 7:43 ` Li Zefan
2010-04-14 13:57 ` [PATCH 0/6] kconfig: add support to show hidden options which " Michal Marek
2010-04-14 23:00 ` Randy Dunlap
2010-04-15 7:29 ` Li Zefan
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=4BC539DD.5040003@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=randy.dunlap@oracle.com \
--cc=tim.bird@am.sony.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