All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: bunk@fs.tum.de, zippel@linux-m68k.org, sam@ravnborg.org,
	linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] select FW_LOADER -> depends HOTPLUG
Date: Wed, 11 Aug 2004 14:25:46 -0700	[thread overview]
Message-ID: <20040811142546.53dc84da.rddunlap@osdl.org> (raw)
In-Reply-To: <20040811111525.GA2205@dmt.cyclades>

On Wed, 11 Aug 2004 08:15:25 -0300 Marcelo Tosatti wrote:

| On Tue, Aug 10, 2004 at 11:16:57PM +0200, 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.
| > 
| > 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. 
| 
| Definately agreed. Not all users want/can go and grep the source 
| tree looking for dependencies of a given 
| symbol.
| 
| Showing the dependencies on menuconfig/xconfig is a user friendly 
| feature. 

xconfig already has a way to do this.  Set all Options (5 of them,
although fewer would probably work).  menuconfig doesn't do this.

What would be even more helpful would be a way to tell *config to
jump from <current location, where a symbol is used> to
<where a symbol is defined>.

--
~Randy

  reply	other threads:[~2004-08-11 21:49 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 [this message]
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=20040811142546.53dc84da.rddunlap@osdl.org \
    --to=rddunlap@osdl.org \
    --cc=bunk@fs.tum.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.com \
    --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.