From: Michal Marek <mmarek@suse.cz>
To: Arnaud Lacombe <lacombar@gmail.com>
Cc: linux-kbuild@vger.kernel.org
Subject: Re: [RFC] kconfig: zconfdump() clean-up
Date: Fri, 24 Jun 2011 16:08:23 +0200 [thread overview]
Message-ID: <4E049A57.1030003@suse.cz> (raw)
In-Reply-To: <1305518795-9360-1-git-send-email-lacombar@gmail.com>
On 16.5.2011 06:06, Arnaud Lacombe wrote:
> Hi Michal,
>
> The following patch is a summarize of changes I made in zconfdump() last week
> when debugging Yann's multiple choice issue. This might help debugging a bit,
> espectially by exposing the tree depth.
>
> Considering the following Kconfig:
>
> config A
> bool "A"
> if A
> choice C
> bool "C"
> config C1
> bool "C1"
> config C2
> bool "C2"
> endchoice
> endif # A
>
> config B
> bool "B"
> depends on ! A
> if B
> choice C
> bool "C"
> config C1
> bool "C1"
> config C2
> bool "C2"
> endchoice
> endif # A
>
> It generates the following output, after menu_finalize():
>
> config A
> boolean
> symbol
> prompt "A"
>
> choice C
> boolean
> symbol
> #choice
> prompt "C" if A
Why not. zconfdump() is only used for debugging and you've been doing
most of the kconfig work lately, so if this suits you, then I'll merge
it. I only spotted one minor issue:
commit 21685d396a123a576bbe487651cb5cc04fa5f9a3
Author: Arnaud Lacombe <lacombar@gmail.com>
Date: Tue May 10 22:55:20 2011 -0400
kconfig/zconfdump(): output newline at the *end* of statement
puts the newline between the symbol statement and it's help text (if
any). So if there is help text defined, it will appear attached to the
next symbol. But it's not really an issue.
Michal
prev parent reply other threads:[~2011-06-24 14:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-16 4:06 [RFC] kconfig: zconfdump() clean-up Arnaud Lacombe
2011-05-16 4:07 ` Arnaud Lacombe
2011-05-31 1:24 ` Arnaud Lacombe
2011-06-08 5:05 ` Arnaud Lacombe
2011-06-24 14:08 ` Michal Marek [this message]
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=4E049A57.1030003@suse.cz \
--to=mmarek@suse.cz \
--cc=lacombar@gmail.com \
--cc=linux-kbuild@vger.kernel.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