All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@fs.tum.de>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: Sam Ravnborg <sam@ravnborg.org>, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] select FW_LOADER -> depends HOTPLUG
Date: Thu, 12 Aug 2004 21:18:59 +0200	[thread overview]
Message-ID: <20040812191859.GN13377@fs.tum.de> (raw)
In-Reply-To: <Pine.LNX.4.58.0408120027330.20634@scrub.home>

On Thu, Aug 12, 2004 at 01:05:47AM +0200, Roman Zippel wrote:
> 
> 
> On Tue, 10 Aug 2004, Sam Ravnborg wrote:
> 
> > On Tue, Aug 10, 2004 at 10:44:11AM +0200, Adrian Bunk wrote:
> > > 
> > > I assume Sam thinks in the direction to let a symbol inherit the 
> > > dependencies off all symbols it selects.
> > > 
> > > E.g. in
> > > 
> > > config A
> > > 	depends on B
> > > 
> > > config C
> > > 	select A
> >         depends on Z
> > 
> >   config Z
> >         depends on Y
> > > 
> > > 
> > > C should be treated as if it would depend on B.
> 
> There are two problems:
> 1) If A has no prompt it's not visible and so it's dependency is 'n', this 
> means a number of symbols wouldn't be visible anymore.
> 2) It would change the bahaviour of symbols, which already do multiple 
> selects (e.g. CONFIG_INET_AH), the select of CRYPTO would be useless, as 
> it would only become visible, when CRYPTO is enabled. This means such 
> selects wouldn't be possible anymore.
> 
> This really needs a different (but similiar) mechanism, what I have in 
> mind is something like this:
> 
> config A
> 	autoselect
> 
> config B
> 	depends on A
> 
> For the visibility calculation A is set to y and A is automatically 
> selected if any symbol, which depends on A, is enabled.
>...

How do you want to handle the following?

<--  snip  -->

config FW_LOADER
      tristate "Hotplug firmware loading support"
      depends on HOTPLUG

config ATMEL
      tristate "Atmel at76c50x chipset  802.11b support"
      depends on NET_RADIO && EXPERIMENTAL
      select FW_LOADER
      select CRC32

<--  snip  -->


We've been biten that often by cases like a "select I2C_ALGOBIT" without 
a dependency on or a select of I2C and such cases are real issues that 
need a proper handling.


> bye, Roman

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:[~2004-08-12 19:19 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 [this message]
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
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=20040812191859.GN13377@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 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.