[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1432285597.27695.55.camel@x220>
Date: Fri, 22 May 2015 11:06:37 +0200
From: Paul Bolle <pebolle@...cali.nl>
To: Takashi Iwai <tiwai@...e.de>
Cc: Geert Uytterhoeven <geert@...ux-m68k.org>,
Borislav Petkov <bp@...en8.de>,
"Luis R. Rodriguez" <mcgrof@...not-panic.com>,
Greg KH <gregkh@...uxfoundation.org>,
"David S. Miller" <davem@...emloft.net>, clemens@...isch.de,
Dmitry Torokhov <dmitry.torokhov@...il.com>,
JBottomley@...n.com, David Airlie <airlied@...ux.ie>,
Mauro Carvalho Chehab <mchehab@....samsung.com>,
Herbert Xu <herbert@...dor.apana.org.au>,
Marcel Holtmann <marcel@...tmann.org>,
"Gustavo F. Padovan" <gustavo@...ovan.org>,
Johan Hedberg <johan.hedberg@...il.com>,
Mikael Starvik <starvik@...s.com>,
Jesper Nilsson <jesper.nilsson@...s.com>,
Imre Kaloz <kaloz@...nwrt.org>, khalasa@...p.pl,
ohad@...ery.com, Arnd Bergmann <arnd@...db.de>, 3chas3@...il.com,
Jiri Slaby <jslaby@...e.cz>, Bryan Wu <cooloney@...il.com>,
Richard Purdie <rpurdie@...ys.net>,
Jacek Anaszewski <j.anaszewski@...sung.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [RFC v1] tree-wide: remove "select FW_LOADER" uses
On Fri, 2015-05-22 at 10:44 +0200, Takashi Iwai wrote:
> At Fri, 22 May 2015 10:17:48 +0200,
> Paul Bolle wrote:
> > Luis also tried to explain to me that disabling FW_LOADER shouldn't make
> > the build fail. (And, of course, we could decide to not care about
> > randconfig builds that have EXPERT set. Maybe we could even special case
> > EXPERT in randconfig. But that would make randconfig builds less useful.
> > That's a separate issue, anyhow.)
>
> But FW_LOADER is a tristate, so it might be inconsistent if selected
> randomly? Luis' patch doesn't add depends but just removes select.
include/linux/firmware.h contains:
#if defined(CONFIG_FW_LOADER) || (defined(CONFIG_FW_LOADER_MODULE) && defined(MODULE)
int request_firmware(const struct firmware **fw, const char *name,
struct device *device);
[...]
#else
static inline int request_firmware(const struct firmware **fw,
const char *name,
struct device *device)
{
return -EINVAL;
}
[...]
#endif
So I _think_ the build should be fine.
But, in case of built-in users of request_firmware() and friends,
actually using that build might not go as expected. But if you set
EXPERT and disable FW_LOADER, or as you point out, set it to 'm', you
own the pieces when things break, don't you?
But now I'm doing Luis' job. I didn't sign off on that patch! So let's
hope Luis thought of all the corner cases.
Paul Bolle
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists