From: Greg KH <greg@kroah.com>
To: Adrian Bunk <bunk@kernel.org>
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: Wed, 11 Jun 2008 11:20:40 -0700 [thread overview]
Message-ID: <20080611182040.GA18506@kroah.com> (raw)
In-Reply-To: <20080611082320.GM11685@cs181133002.pp.htv.fi>
On Wed, Jun 11, 2008 at 11:23:20AM +0300, Adrian Bunk wrote:
> On Tue, Jun 10, 2008 at 02:28:59PM -0700, Greg KH wrote:
> > On Tue, Jun 10, 2008 at 09:12:06PM +0300, Adrian Bunk wrote:
> > > 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).
> >
> > Ok, but what about the point that the options that are wanting FW_LOADER
> > in that situation? I know EMBEDDED is tough to get right as you can
> > shoot yourself in the foot very easily, but this seems like we are going
> > to make it even harder to use properly.
>
> Currently missing selects can result in a build error.
>
> After James' patch to fix the dummy functions (that should have worked
> from day 1) it will instead become a runtime problem.
Ah, yes, that should be fine then.
Can you bounce me the patch again?
thanks,
greg k-h
next prev parent reply other threads:[~2008-06-11 18:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-10 16:04 [2.6 patch] always enable FW_LOADER unless EMBEDDED=y Adrian Bunk
2008-06-10 16:24 ` Greg KH
2008-06-10 18:12 ` Adrian Bunk
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 [this message]
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=20080611182040.GA18506@kroah.com \
--to=greg@kroah.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akpm@linux-foundation.org \
--cc=bunk@kernel.org \
--cc=dwmw2@infradead.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