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] xconfig: Display dependency values in debug_info
Date: Thu, 26 Jul 2012 10:02:10 -0700 [thread overview]
Message-ID: <50117812.5080302@xenotime.net> (raw)
In-Reply-To: <CA+jpPM=nrbpDJpaka6xAp4dbEOQjJrtwQWtUXwi_gGS9b4yK-A@mail.gmail.com>
On 07/26/2012 09:19 AM, Salar Ali Mumtaz wrote:
> Hi.
>
> Thanks for the quick reply.
>
> This adds the current values to the dependencies in the debug_info, which you get when you select "Show debug info"
> from the popup you get after you right click. For some values, there is no help available. For those, there is usually
> information in the debug_info that is not displayed normally.
>
> COMPAT_BINFMT_ELF
>
> //This is added by debug_info
> type: boolean
> reverse dep: (IA32_EMULATION n && X86_64 n ) =n
> unknown property: symbol
> dep: ( COMPAT n && BINFMT_ELF y ) =n
> //This is added by debug_info
>
> defined at fs/Kconfig.binfmt:26
>
> There is no help available for this option.
> Symbol: COMPAT_BINFMT_ELF [=n]
> Type : boolean
> Selected by: IA32_EMULATION [=n] && X86_64 [=n]
>
> Hope this helps.
>
Yes, it does help. Thanks.
For BINFMT_ELF (not your example of COMPAT_BINFMT_ELF)
in Linux 3.5, I see this:
BEFORE PATCH:
type: boolean
unknown property: symbol
dep: MMU && (BROKEN || !FRV)
prompt: Kernel support for ELF binaries
dep: MMU && (BROKEN || !FRV)
default: y
dep: MMU && (BROKEN || !FRV)
defined at fs/Kconfig.binfmt:1
AFTER PATCH:
type: boolean
unknown property: symbol
dep: ( MMU y && (BROKEN n || !FRV FRV) ) =y
prompt: Kernel support for ELF binaries
dep: ( MMU y && (BROKEN n || !FRV FRV) ) =y
default: y
dep: ( MMU y && (BROKEN n || !FRV FRV) ) =y
defined at fs/Kconfig.binfmt:1
The added y/n/m are clear, but the "!FRV FRV" is confusing,
isn't it?
--
~Randy
next prev parent reply other threads:[~2012-07-26 17:03 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 [this message]
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=50117812.5080302@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.