public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Manuel Estrada Sainz <ranty@debian.org>
To: Greg KH <greg@kroah.com>, LKML <linux-kernel@vger.kernel.org>,
	Simon Kelley <simon@thekelleys.org.uk>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	jt@hpl.hp.com, Pavel Roskin <proski@gnu.org>,
	Oliver Neukum <oliver@neukum.org>,
	David Gibson <david@gibson.dropbear.id.au>,
	zippel@linux-m68k.org
Subject: Re: [PATCH] Re: request_firmware() hotplug interface, third round and a halve
Date: Thu, 22 May 2003 08:26:03 +0200	[thread overview]
Message-ID: <20030522062603.GA13224@ranty.ddts.net> (raw)
In-Reply-To: <20030521215116.GA3441@mars.ravnborg.org>

On Wed, May 21, 2003 at 11:51:16PM +0200, Sam Ravnborg wrote:
> On Wed, May 21, 2003 at 08:52:12PM +0200, Manuel Estrada Sainz wrote:
> >  
> >  Maybe kbuild could allow forcing one option from another, a companion
> >  for 'depends', lets call it 'hard_depends'
> > 
> > 	 depends FOO
> > 		If FOO is not there the entry won't even be shown in the
> > 		menu.
> > 	 hard_depends FOO 
> > 		FOO gets set to satisfy the dependency.
> > 
> 
> Roman Zippel introduced: "enable" in his latest Kconfig goodies:
> http://marc.theaimsgroup.com/?l=linux-kernel&m=105274692328723&w=2
> 
> Would that be usefull for you?
> This would allow you to set CONFIG_LOADER for the drivers that
> really needs it.

 Yep, that is perfect.
 
> IIRC this is not included in Linus-BK yet.

 Nop :( once it is in, I'll start using it. Oh, and I volunteer to
 cleanup the CRC32 stuff on top of that :)

 Have a nice day

 	Manuel

-- 
--- Manuel Estrada Sainz <ranty@debian.org>
                         <ranty@bigfoot.com>
			 <ranty@users.sourceforge.net>
------------------------ <manuel.estrada@hispalinux.es> -------------------
Let us have the serenity to accept the things we cannot change, courage to
change the things we can, and wisdom to know the difference.

      reply	other threads:[~2003-05-22  6:13 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-17 22:19 request_firmware() hotplug interface, third round and a halve Manuel Estrada Sainz
2003-05-21  7:23 ` Greg KH
2003-05-21  7:44   ` David Gibson
2003-05-21 18:36     ` Manuel Estrada Sainz
2003-05-21 18:34   ` Manuel Estrada Sainz
2003-05-21 19:03     ` Greg KH
2003-05-21 18:52   ` [PATCH] " Manuel Estrada Sainz
2003-05-21 20:07     ` Greg KH
2003-05-22 15:31       ` Manuel Estrada Sainz
2003-05-22 16:14         ` Patrick Mochel
2003-05-22 16:34           ` Manuel Estrada Sainz
2003-05-22 16:38             ` Patrick Mochel
2003-05-22 16:43               ` Manuel Estrada Sainz
2003-05-22 16:51                 ` Patrick Mochel
2003-05-22 17:01                   ` Manuel Estrada Sainz
2003-05-22 17:03                     ` Patrick Mochel
2003-05-22 17:57         ` Simon Kelley
2003-05-22 18:15           ` Manuel Estrada Sainz
2003-05-21 21:51     ` Sam Ravnborg
2003-05-22  6:26       ` Manuel Estrada Sainz [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=20030522062603.GA13224@ranty.ddts.net \
    --to=ranty@debian.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=david@gibson.dropbear.id.au \
    --cc=greg@kroah.com \
    --cc=jt@hpl.hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oliver@neukum.org \
    --cc=proski@gnu.org \
    --cc=simon@thekelleys.org.uk \
    --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