From: Adrian Bunk <bunk@fs.tum.de>
To: Roman Zippel <zippel@linux-m68k.org>,
Sam Ravnborg <sam@ravnborg.org>,
linux-kernel@vger.kernel.org
Subject: Re: menuconfig displays dependencies [Was: select FW_LOADER -> depends HOTPLUG]
Date: Sun, 15 Aug 2004 22:45:55 +0200 [thread overview]
Message-ID: <20040815204555.GS1387@fs.tum.de> (raw)
In-Reply-To: <20040815203245.GA14336@mars.ravnborg.org>
On Sun, Aug 15, 2004 at 10:32:45PM +0200, Sam Ravnborg wrote:
> On Sun, Aug 15, 2004 at 10:21:11PM +0200, Adrian Bunk wrote:
> > > CONFIG_FOO
> > >
> > > Depends on:
> > > CONFIG_BAR: [ ] "Prompt for BAR"
> >
> >
> > Assuming I'm configuring a kernel for i386, what should I see when
> > pressing 'd' on the following driver?
> >
> >
> > config OAKNET
> > tristate "National DP83902AV (Oak ethernet) support"
> > depends on NET_ETHERNET && PPC && BROKEN
> > select CRC32
> >
> What about:
> Depends on:
> [ ] "Prompt for NET_ETHERNET" (CONFIG_NET_ETHERNET)
> --- "Promt ..." (CONFIG_PPC)
> --- " Prompt ... " (CONFIG_BROKEN)
CONFIG_BROKEN is available.
And in other cases, e.g. I2C_ALGOBIT might be a dependency, but depends
itself on I2C which might be disabled.
> Selects
> "Prompt for CRC32)" (CONFIG_CRC32)
>
> That would make sense to me at least.
Showing all !i386 drivers on i386 will make it harder for people to find
the drivers they actually need.
> If I ever look into it I will touch upon the corner cases for sure.
Thanks.
BTW:
"make oldconfig" will need a similar treatment before we can start
changing selects to depends.
> Sam
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
next prev parent reply other threads:[~2004-08-15 20:46 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-09 19:56 [2.6 patch] select FW_LOADER -> depends HOTPLUG Adrian Bunk
2004-08-09 20:08 ` Adrian Bunk
2004-08-09 20:26 ` Marcelo Tosatti
2004-08-09 22:05 ` Adrian Bunk
2004-08-09 20:38 ` Sam Ravnborg
2004-08-10 0:24 ` Roman Zippel
2004-08-10 8:44 ` Adrian Bunk
2004-08-10 21:16 ` Sam Ravnborg
2004-08-11 11:15 ` Marcelo Tosatti
2004-08-11 21:25 ` Randy.Dunlap
2004-08-11 23:05 ` Roman Zippel
2004-08-12 19:18 ` Adrian Bunk
2004-08-15 17:06 ` Roman Zippel
2004-08-14 7:49 ` menuconfig displays dependencies [Was: select FW_LOADER -> depends HOTPLUG] Sam Ravnborg
2004-08-14 18:12 ` Randy.Dunlap
2004-08-14 21:05 ` Adrian Bunk
2004-08-14 22:37 ` Sam Ravnborg
2004-08-15 20:21 ` Adrian Bunk
2004-08-15 20:32 ` Sam Ravnborg
2004-08-15 20:45 ` Adrian Bunk [this message]
2004-08-15 17:35 ` Roman Zippel
2004-08-15 17:40 ` Adrian Bunk
2004-08-15 22:47 ` Roman Zippel
2004-08-16 19:57 ` Adrian Bunk
2004-08-16 20:07 ` Russell King
2004-08-16 20:22 ` Adrian Bunk
2004-08-16 20:39 ` Roman Zippel
2004-08-15 17:28 ` Roman Zippel
2004-08-15 17:58 ` Sam Ravnborg
2004-08-15 22:49 ` 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=20040815204555.GS1387@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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