From: Adrian Bunk <bunk@kernel.org>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org,
David Woodhouse <dwmw2@infradead.org>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [2.6 patch] always enable FW_LOADER unless EMBEDDED=y
Date: Tue, 10 Jun 2008 21:12:06 +0300 [thread overview]
Message-ID: <20080610181206.GF11685@cs181133002.pp.htv.fi> (raw)
In-Reply-To: <20080610162450.GB13538@kroah.com>
On Tue, Jun 10, 2008 at 09:24:50AM -0700, Greg KH wrote:
> On Tue, Jun 10, 2008 at 07:04:08PM +0300, Adrian Bunk wrote:
> > James Bottomley recently discovered that we have
> > {request,release}_firmware() dummies for the case of the actual
> > functions not being available and has a fix for the bug that was
> > actually causing build errors for built-in users with
> > CONFIG_FW_LOADER=m.
> >
> > But now missing selects on FW_LOADER are no longer visible at
> > compile-time at all and can become runtime problems.
> >
> > FW_LOADER is infrastructure with relatively small codesize we can
> > safely enable for everyone, and only for people who really need small
> > kernels (and can be expected to know what they are doing) it matters
> > being able to disable it.
> >
> > This patch therefore always sets FW_LOADER=y and allows users only to
> > disable it with EMBEDDED=y.
> >
> > As a bonus, we can then get rid of all "select FW_LOADER" plus the due
> > to it required "depends on HOTPLUG" which removes some complexity from
> > our Kconfig files.
>
> Well, we can't get rid of that if EMBEDDED is set, right?
No, if EMBEDDED is set and HOTPLUG is not set you will not be able to
enable FW_LOADER (the "depends on HOTPLUG" for FW_LOADER has to stay,
but all the options that currently select FW_LOADER no longer need the
dependency).
> You sent this as an RFC before, I thought people said to just fix up all
> of the dependancies with drivers that needed FW_LOADER to be enabled,
> that would be easier, right?
As far as I know there were zero answers to my RFC.
What are you referring to?
> thanks,
>
> greg k-h
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
next prev parent reply other threads:[~2008-06-10 18:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-10 16:04 Adrian Bunk
2008-06-10 16:24 ` Greg KH
2008-06-10 18:12 ` Adrian Bunk [this message]
2008-06-10 21:28 ` Greg KH
2008-06-11 8:23 ` Adrian Bunk
2008-06-11 9:20 ` Boaz Harrosh
2008-06-11 9:59 ` Adrian Bunk
2008-06-11 11:41 ` Boaz Harrosh
2008-06-11 18:20 ` Greg KH
2008-06-11 19:38 ` Adrian Bunk
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=20080610181206.GF11685@cs181133002.pp.htv.fi \
--to=bunk@kernel.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akpm@linux-foundation.org \
--cc=dwmw2@infradead.org \
--cc=greg@kroah.com \
--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
all inboxes | Powered by JetHome®