The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: Roman Zippel <zippel@linux-m68k.org>,
	Sam Ravnborg <sam@ravnborg.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] select FW_LOADER -> depends HOTPLUG
Date: Tue, 10 Aug 2004 23:16:57 +0200	[thread overview]
Message-ID: <20040810211656.GA7221@mars.ravnborg.org> (raw)
In-Reply-To: <20040810084411.GI26174@fs.tum.de>

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.

Correct. But at the same time I miss some functionality to
tell me what a given symbol:
1) depends on
2) selects

It would be nice in menuconfig to see what config symbol
that has dependencies and/or side effects. 

[*] PCI support
Could look like:
[*]d PCI support
The space for the 'd' tag could be misused for other purposes later.


The pressing 'd' would give me the following output:

C "The C prompt"
-> depends on
   CONFIG_Z "Prompt for Z"
   -> depends on
      CONFIG_Y "Prompt for Y"
-> Selects
   CONFIG_A "Promtp for A"
   -> depends on
      CONFIG_B "Prompt for B"

Or something similar.
The idea is to give user an idea of dependencies (both ways) - recursive.
Using both CONFIG symbol and prompt will give the user an idea where to
locate it.

Something like this is on my wish list.

	Sam

  reply	other threads:[~2004-08-10 21:14 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 [this message]
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
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=20040810211656.GA7221@mars.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=bunk@fs.tum.de \
    --cc=linux-kernel@vger.kernel.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