linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Salar Ali Mumtaz <salaarali@gmail.com>
To: Michal Marek <mmarek@suse.cz>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
	Salar Ali Mumtaz <salaarali@gmail.com>
Subject: [PATCH] xconfig: Display dependency values in debug_info
Date: Wed, 25 Jul 2012 18:56:22 -0400	[thread overview]
Message-ID: <1343256982-11421-1-git-send-email-salaarali@gmail.com> (raw)

Displays the current value of each of the dependencies of a menu item.
Before, you needed to do tedious searching to find out the current values
of the dependences. Now they all are included in the debug_info, making
the task easier

Signed-off-by: Salar Ali Mumtaz <salaarali@gmail.com>
---
 scripts/kconfig/qconf.cc |   10 +++++++++-
 1 files changed, 9 insertions(+), 1 deletions(-)

diff --git a/scripts/kconfig/qconf.cc b/scripts/kconfig/qconf.cc
index df274fe..abd500f 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 += "&nbsp;&nbsp;&nbsp;&nbsp;dep: ";
+			debug += " ( ";
 			expr_print(prop->visible.expr, expr_print_help, &debug, E_NONE);
+			debug += " )  =";
+			debug += print_filter(sym_get_string_value(sym));
 			debug += "<br>";
 		}
 	}
@@ -1157,6 +1162,9 @@ void ConfigInfoView::expr_print_help(void *data, struct symbol *sym, const char
 		*text += QString().sprintf("<a href=\"s%p\">", sym);
 		*text += str2;
 		*text += "</a>";
+		*text += "<b>   ";
+		*text += print_filter(sym_get_string_value(sym));
+		*text += "</b>";
 	} else
 		*text += str2;
 }
-- 
1.7.5.4


             reply	other threads:[~2012-07-25 22:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-25 22:56 Salar Ali Mumtaz [this message]
2012-07-25 23:18 ` [PATCH] xconfig: Display dependency values in debug_info 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
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=1343256982-11421-1-git-send-email-salaarali@gmail.com \
    --to=salaarali@gmail.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmarek@suse.cz \
    /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).