[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150521222129.GI3689@pd.tnic>
Date: Fri, 22 May 2015 00:21:29 +0200
From: Borislav Petkov <bp@...en8.de>
To: "Luis R. Rodriguez" <mcgrof@...not-panic.com>
Cc: gregkh@...uxfoundation.org, davem@...emloft.net,
clemens@...isch.de, dmitry.torokhov@...il.com, JBottomley@...n.com,
airlied@...ux.ie, mchehab@....samsung.com,
herbert@...dor.apana.org.au, marcel@...tmann.org,
gustavo@...ovan.org, johan.hedberg@...il.com, starvik@...s.com,
jesper.nilsson@...s.com, kaloz@...nwrt.org, khalasa@...p.pl,
ohad@...ery.com, arnd@...db.de, 3chas3@...il.com, jslaby@...e.cz,
cooloney@...il.com, rpurdie@...ys.net, j.anaszewski@...sung.com,
pebolle@...cali.nl, tiwai@...e.de, linux-kernel@...r.kernel.org
Subject: Re: [RFC v1] tree-wide: remove "select FW_LOADER" uses
On Thu, May 21, 2015 at 01:45:49PM -0700, Luis R. Rodriguez wrote:
> The above history is just *one* set of reasons to remove all kernel
> "select FW_LOADER" entries. Another simple reason is that since
> FW_LOADER can only be disabled by an EXPERT and it defaults to y
> its now a superfluous select. We will ensure things build for you
> if using EXPERT but if you have selected EXPERT you should know
> what run time requirements you need.
Couple of notes only:
So the "depends" thing is a step backwards IMO because people would have
to go and enable FW_LOADER first. For the microcode loader, at least,
"select" is perfectly fine.
There's also the other aspect that this FW_LOADER thing ends up enabled
on 99.9% (!?) of the distro installations anyway, right? I.e., there's
always something needing firmware from userspace.
So the current "default y" behind EXPERT is probably the correct thing
anyway.
So yeah, send me the x86 microcode loader patch, I'll take it.
Thanks.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
--
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