public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Bodo Eggert <7eggert@gmx.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Documentation mismatch in Documentation/kbuild/kconfig-language.txt
Date: Sat, 9 Jul 2005 11:36:57 +0200	[thread overview]
Message-ID: <20050709093657.GG28243@stusta.de> (raw)
In-Reply-To: <Pine.LNX.4.58.0507090934510.4231@be1.lrz>

On Sat, Jul 09, 2005 at 09:37:48AM +0200, Bodo Eggert wrote:
> On Sat, 9 Jul 2005, Adrian Bunk wrote:
> > On Mon, Jul 04, 2005 at 04:59:18PM +0200, Bodo Eggert wrote:
> 
> ...
> > > Therefore I can't use
> > > config SGI_IOC4
> > >     tristate
> > >     prompt "SGI IOC4 Base IO support" if PROMPT_FOR_UNUSED_CORES
> > >     depends on (IA64_GENERIC || IA64_SGI_SN2) && MMTIMER
> > >     default n
> ...
> > > Since the "if" is useless, misleading and redundand with this behaviour, I 
> > > suggest stripping it out.
> > 
> > "if" is valuable in "default y" cases.
> 
> It should be, but either it's really applied to the config instead of the 
> prompt (in which can also be added to the depends on list) or the 
> menuconfig '/' function has bogus output.

config FUTEX
        bool "Enable futex support" if EMBEDDED
        default y

This option is always "y" if EMBEDDED=n.
This option is uservisible if EMBEDDED=y.

I don't understand what's not working for you in this case.

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2005-07-09  9:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-04 14:59 Documentation mismatch in Documentation/kbuild/kconfig-language.txt Bodo Eggert
2005-07-08 22:17 ` Adrian Bunk
2005-07-09  7:37   ` Bodo Eggert
2005-07-09  9:36     ` Adrian Bunk [this message]
2005-07-09 21:14       ` Bodo Eggert
2005-07-09 13:24     ` Roman Zippel

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=20050709093657.GG28243@stusta.de \
    --to=bunk@stusta.de \
    --cc=7eggert@gmx.de \
    --cc=linux-kernel@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