public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] FW_LOADER should select HOTPLUG
Date: Sun, 3 Dec 2006 10:17:15 +0100	[thread overview]
Message-ID: <20061203091715.GA3442@stusta.de> (raw)
In-Reply-To: <20061203012401.3cc30232.akpm@osdl.org>

On Sun, Dec 03, 2006 at 01:24:01AM -0800, Andrew Morton wrote:
> On Sun, 3 Dec 2006 09:15:52 +0100
> Adrian Bunk <bunk@stusta.de> wrote:
> 
> > On Sun, Dec 03, 2006 at 12:58:24AM -0800, Andrew Morton wrote:
> > > On Sun, 3 Dec 2006 08:16:37 +0100
> > > Adrian Bunk <bunk@stusta.de> wrote:
> > > 
> > > > Since FW_LOADER is an option that is always select'ed by the code using 
> > > > it, it mustn't depend on HOTPLUG.
> > > > 
> > > > It's only relevant in the EMBEDDED=y case, but this might have resulted 
> > > > in illegal FW_LOADER=, HOTPLUG=n configurations.
> > > > 
> > > > Signed-off-by: Adrian Bunk <bunk@stusta.de>
> > > > 
> > > > --- linux-2.6.19-rc6-mm2/drivers/base/Kconfig.old	2006-12-02 20:36:49.000000000 +0100
> > > > +++ linux-2.6.19-rc6-mm2/drivers/base/Kconfig	2006-12-02 20:37:03.000000000 +0100
> > > > @@ -19,8 +19,8 @@
> > > >  	  If unsure say Y here.
> > > >  
> > > >  config FW_LOADER
> > > > -	tristate "Userspace firmware loading support"
> > > > -	depends on HOTPLUG
> > > > +	tristate
> > > > +	select HOTPLUG
> > > 
> > > It would be a retrograde step to start selecting HOTPLUG - we've managed to
> > > avoid it thus far.
> > 
> > $ grep -r "select HOTPLUG" * | wc -l
> > 4
> > $ 
> > 
> > > It'd be better to make those drivers which select FW_LOADER dependent upon
> > > HOTPLUG.
> > 
> > $ grep -r "select FW_LOADER" * | wc -l
> > 71
> 
> 46 actually.  And it's immaterial.

Sorry, I had some .old and .orig files in my tree...

> > And since the only case where depends<->select makes a difference is 
> > CONFIG_EMBEDDED=y, people will always continue to forget the dependency 
> > on HOTPLUG when select'ing FW_LOADER.
> 
> I realise that.  But having HOTPLUG magically and mysteriously turn itself
> back on again is a pita.

In practice, it's already always turned on (except for CONFIG_EMBEDDED=n).

Unless Kconfig gets changed to automatically inherit dependencies of 
select'ed symbols, FW_LOADER not select'ing HOTPLUG is simply a constant 
source of bugs.

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:[~2006-12-03  9:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-02 19:40 [2.6 patch] FW_LOADER should select HOTPLUG Adrian Bunk
2006-12-03  7:16 ` Adrian Bunk
2006-12-03  8:58   ` Andrew Morton
2006-12-03  8:15     ` Adrian Bunk
2006-12-03  9:24       ` Andrew Morton
2006-12-03  9:17         ` Adrian Bunk [this message]

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=20061203091715.GA3442@stusta.de \
    --to=bunk@stusta.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.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