All of lore.kernel.org
 help / color / mirror / Atom feed
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: Mon, 16 Aug 2004 22:22:53 +0200	[thread overview]
Message-ID: <20040816202253.GC1387@fs.tum.de> (raw)
In-Reply-To: <20040816210729.A25893@flint.arm.linux.org.uk>

On Mon, Aug 16, 2004 at 09:07:30PM +0100, Russell King wrote:
> 
> Let me make my position over the use of "select" clear: I do not
> oppose its appropriate use, where that is defined as selecting
> another configuration option for which the user has no visibility.
> 
> In the above case, it _may_ make sense (I haven't looked deeply
> into it yet) to:
> 
> - make _all_ drivers which need FW_LOADER select it
> - make _all_ drivers which currently depend on HOTPLUG select it
> - make FW_LOADER select HOTPLUG
> - remove user questions for FW_LOADER and HOTPLUG
> 
> That means that FW_LOADER and HOTPLUG are automatically selected
> whenever the configuration requires them and are automatically
> deselected when it doesn't need them, and you don't have to worry
> about whether you can disable them now or after finding the
> thousand and one configuration symbols which need to be turned off
> first.
> 
> However, keeping the option user-visible _and_ using select is
> problematical to say the least.

Currently, I see no good alternative to e.g. USB_STORAGE selecting SCSI.
Enhanchements to _all_ kernel configuration tools are required before 
this can be changed.

But it still leaves the problem that modules not included in the kernel  
might require the functionality provided by such an option.
Even CRC32 is user-visible.

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-16 20:23 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
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 [this message]
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=20040816202253.GC1387@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.