From: Randy Dunlap <rdunlap@xenotime.net>
To: Salar Ali Mumtaz <salaarali@gmail.com>
Cc: Michal Marek <mmarek@suse.cz>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] xconfig: Display dependency values in debug_info
Date: Tue, 31 Jul 2012 13:21:59 -0700 [thread overview]
Message-ID: <50183E67.1060509@xenotime.net> (raw)
In-Reply-To: <50182ACF.6070704@gmail.com>
On 07/31/2012 11:58 AM, Salar Ali Mumtaz wrote:
> Now the debug_info only shows y/n/m values.
>
or no value at all??
for CONFIG_BINFMT_ELF:
Kernel support for ELF binaries (BINFMT_ELF)
type: boolean
unknown property: symbol
dep: ( MMU y && (BROKEN n || !FRV ) ) =y
prompt: Kernel support for ELF binaries
dep: ( MMU y && (BROKEN n || !FRV ) ) =y
default: y
dep: ( MMU y && (BROKEN n || !FRV ) ) =y
defined at fs/Kconfig.binfmt:1
CONFIG_BINFMT_ELF:
> Signed-off-by: Salar Ali Mumtaz <salaarali@gmail.com>
> ---
> scripts/kconfig/qconf.cc | 14 +++++++++++++-
> 1 files changed, 13 insertions(+), 1 deletions(-)
>
> diff --git a/scripts/kconfig/qconf.cc b/scripts/kconfig/qconf.cc
> index df274fe..b6a7cc5 100644
> --- a/scripts/kconfig/qconf.cc
> +++ b/scripts/kconfig/qconf.cc
> @@ -1073,8 +1073,10 @@ QString ConfigInfoView::debug_info(struct symbol *sym)
> debug += " (choice)";
> debug += "<br>";
> if (sym->rev_dep.expr) {
> - debug += "reverse dep: ";
> + debug += "reverse dep: (";
> expr_print(sym->rev_dep.expr, expr_print_help, &debug, E_NONE);
> + debug += " ) =";
> + debug += print_filter(sym_get_string_value(sym));
> debug += "<br>";
> }
> for (struct property *prop = sym->prop; prop; prop = prop->next) {
> @@ -1108,7 +1110,10 @@ QString ConfigInfoView::debug_info(struct symbol *sym)
> }
> if (prop->visible.expr) {
> debug += " dep: ";
> + debug += " ( ";
> expr_print(prop->visible.expr, expr_print_help, &debug, E_NONE);
> + debug += " ) =";
> + debug += print_filter(sym_get_string_value(sym));
> debug += "<br>";
> }
> }
> @@ -1152,11 +1157,18 @@ void ConfigInfoView::expr_print_help(void *data, struct symbol *sym, const char
> {
> QString* text = reinterpret_cast<QString*>(data);
> QString str2 = print_filter(str);
> + QString value;
>
> if (sym && sym->name && !(sym->flags & SYMBOL_CONST)) {
> + value = print_filter(sym_get_string_value(sym));
> +
> *text += QString().sprintf("<a href=\"s%p\">", sym);
> *text += str2;
> *text += "</a>";
> + *text += "<b> ";
> + if(value == "y" || value == "m" || value == "n")
> + *text += print_filter(sym_get_string_value(sym));
> + *text += "</b>";
> } else
> *text += str2;
> }
thanks,
--
~Randy
next prev parent reply other threads:[~2012-07-31 23:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-25 22:56 [PATCH] xconfig: Display dependency values in debug_info Salar Ali Mumtaz
2012-07-25 23:18 ` Randy Dunlap
[not found] ` <CA+jpPM=nrbpDJpaka6xAp4dbEOQjJrtwQWtUXwi_gGS9b4yK-A@mail.gmail.com>
2012-07-26 17:02 ` Randy Dunlap
2012-07-31 16:51 ` Salar Ali Mumtaz
2012-07-31 18:58 ` [PATCH v2] " Salar Ali Mumtaz
2012-07-31 20:21 ` Randy Dunlap [this message]
2012-08-02 4:20 ` Salar Ali Mumtaz
2012-08-02 4:47 ` Randy Dunlap
2012-08-07 16:08 ` [PATCH] " Salar Ali Mumtaz
2012-08-07 16:55 ` Randy Dunlap
2012-08-09 18:54 ` Salar Ali Mumtaz
2012-08-11 0:39 ` Randy Dunlap
2012-08-15 16:32 ` Salar Ali Mumtaz
2012-08-15 17:29 ` Randy Dunlap
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=50183E67.1060509@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=salaarali@gmail.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).