From: Blaisorblade <blaisorblade@yahoo.it>
To: linux-ia64@vger.kernel.org
Subject: Re: Kconfig bug (was: Re: fault-injection framework on ia64)
Date: Fri, 16 Feb 2007 20:10:42 +0000 [thread overview]
Message-ID: <200702162110.42608.blaisorblade@yahoo.it> (raw)
In-Reply-To: <200702161938.17340.blaisorblade@yahoo.it>
On Friday 16 February 2007 20:12, Roman Zippel wrote:
> Hi,
>
> On Fri, 16 Feb 2007, Blaisorblade wrote:
> > However, more important, if I remove STACKTRACE_SUPPORT, or if I make
> > it 'default n', FAULT_INJECTION can still be enabled, even if it selects
> > STACKTRACE which has a failed dependency (tested on UML). Which is a
> > Kconfig bug - if A selects B and B depends on C, no dependency of A on C
> > is deduced. Right Roman?
>
> Correct, but could someone please give me some more context, what the bug
> is supposed to be here?
Hmm.
You agree that "if A selects B and B depends on C, no dependency of A on C is
deduced", right?
The implication is that the user can enable A, which selects B, while C is
still disabled. The B -> C dependency is violated, and the build will fail or
bad things will happen.
I hope things are now clearer, even without the description of the testcase
where this happened.
--
Inform me of my mistakes, so I can add them to my list!
Paolo Giarrusso, aka Blaisorblade
http://www.user-mode-linux.org/~blaisorblade
Chiacchiera con i tuoi amici in tempo reale!
http://it.yahoo.com/mail_it/foot/*http://it.messenger.yahoo.com
next prev parent reply other threads:[~2007-02-16 20:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-16 18:38 Kconfig bug (was: Re: fault-injection framework on ia64) Blaisorblade
2007-02-16 19:12 ` Roman Zippel
2007-02-16 20:10 ` Blaisorblade [this message]
2007-02-16 22:26 ` Roman Zippel
2007-02-17 0:06 ` Blaisorblade
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=200702162110.42608.blaisorblade@yahoo.it \
--to=blaisorblade@yahoo.it \
--cc=linux-ia64@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