linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miles Bader <miles@lsi.nec.co.jp>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] new kconfig goodies
Date: 13 May 2003 10:44:01 +0900	[thread overview]
Message-ID: <buou1bz7h9a.fsf@mcspd15.ucom.lsi.nec.co.jp> (raw)
In-Reply-To: <Pine.LNX.4.44.0305111838300.14274-100000@serv>

Roman Zippel <zippel@linux-m68k.org> writes:
> BTW this clears my todo list of important features for the kconfig syntax 
> itself, if you think there is something missing, please tell me now, 
> otherwise it might have to wait for 2.7.

Hi, I sent the following about kconfig a while ago, but never got an
answer; do you have any comment on it?

Here's the message:

> I have the following two entries in my Kconfig file (arch/v850/Kconfig):
>
>    config RTE_CB_MULTI
>    	  bool
> 	  # RTE_CB_NB85E can either have multi ROM support or not, but
> 	  # other platforms (currently only RTE_CB_MA1) require it.
> 	  prompt "Multi monitor ROM support" if RTE_CB_NB85E
> 	  depends RTE_CB
> 	  default y
>
>    config RTE_CB_MULTI_DBTRAP
>    	  bool "Pass illegal insn trap / dbtrap to kernel"
> 	  depends RTE_CB_MULTI
> 	  default n
>
> What I expect this to do is to only ask the first question (RTE_CB_MULTI)
> if RTE_CB_NB85E is true and otherwise just assume true -- this part
> seems to work correctly -- but to _always_ ask the second question
> (RTE_CB_MULTI_DBTRAP) as long as its dependencies are true.
>
> However, what happens in practice is that the second question is only
> displayed if the first question is displayed (the resulting actual value
> of RTE_CB_MULTI_DBTRAP is whatever value it had before I entered the
> menuconfig).
>
> So... is this a bug?  If not, is there some other way I can have a
> question [a] depend on another question [b], where [b] is optional
> (defaulting to y), but [a] is not?

[I haven't tested this recently, so I suppose it could have silently
been fixed.]

Thanks,

-Miles
-- 
Would you like fries with that?

  parent reply	other threads:[~2003-05-13  1:31 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-12 13:39 [PATCH] new kconfig goodies Roman Zippel
2003-05-12 14:16 ` Adrian Bunk
2003-05-12 15:37   ` Roman Zippel
2003-05-12 14:32 ` Dave Jones
2003-05-12 15:39   ` Roman Zippel
2003-05-12 16:08     ` Dave Jones
2003-05-12 16:00   ` Tomas Szepe
2003-05-12 22:36     ` Roman Zippel
2003-05-12 15:13 ` Geert Uytterhoeven
2003-05-12 15:43   ` Roman Zippel
2003-05-13  1:38 ` Miles Bader
2003-05-13  1:44 ` Miles Bader [this message]
2003-05-13 15:27   ` Roman Zippel
2003-05-13 21:17     ` Miles Bader
2003-05-14 19:51       ` Roman Zippel
2003-05-14 20:56         ` Andreas Schwab
2003-05-14 22:11           ` Roman Zippel
2003-05-15  0:21             ` Michael Alan Dorman

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=buou1bz7h9a.fsf@mcspd15.ucom.lsi.nec.co.jp \
    --to=miles@lsi.nec.co.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miles@gnu.org \
    --cc=zippel@linux-m68k.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;
as well as URLs for NNTP newsgroup(s).