Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756636AbbEVIR7 (ORCPT ); Fri, 22 May 2015 04:17:59 -0400 Received: from lb3-smtp-cloud3.xs4all.net ([194.109.24.30]:43779 "EHLO lb3-smtp-cloud3.xs4all.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756513AbbEVIR4 (ORCPT ); Fri, 22 May 2015 04:17:56 -0400 Message-ID: <1432282668.27695.24.camel@x220> Subject: Re: [RFC v1] tree-wide: remove "select FW_LOADER" uses From: Paul Bolle To: Geert Uytterhoeven Cc: Borislav Petkov , "Luis R. Rodriguez" , Greg KH , "David S. Miller" , clemens@ladisch.de, Dmitry Torokhov , JBottomley@odin.com, David Airlie , Mauro Carvalho Chehab , Herbert Xu , Marcel Holtmann , "Gustavo F. Padovan" , Johan Hedberg , Mikael Starvik , Jesper Nilsson , Imre Kaloz , khalasa@piap.pl, ohad@wizery.com, Arnd Bergmann , 3chas3@gmail.com, Jiri Slaby , Bryan Wu , Richard Purdie , Jacek Anaszewski , Takashi Iwai , "linux-kernel@vger.kernel.org" Date: Fri, 22 May 2015 10:17:48 +0200 In-Reply-To: References: <1432241149-8762-1-git-send-email-mcgrof@do-not-panic.com> <20150521222129.GI3689@pd.tnic> <20150522065346.GA23022@pd.tnic> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.10.4 (3.10.4-4.fc20) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1627 Lines: 40 On Fri, 2015-05-22 at 09:11 +0200, Geert Uytterhoeven wrote: > On Fri, May 22, 2015 at 8:53 AM, Borislav Petkov wrote: > > One thing I forgot last night: what about randconfigs? All that > > functionality which selects FW_LOADER, won't boot anymore, right? I > > mean, there are provisions to build fine even with FW_LOADER unset but > > if you want to boot-test those kernels, you will artificially fail due > > to missing request_firmware* things... 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.) > If you expect to _boot_ randconfig kernels, you better disable EXPERT. > Still, your kernel can fail to boot due to some other critical dependency > (does your kernel support your CPU?). > > If you want to boot randconfig kernels, create an allrandomconfig file > listing all options that must have a certain value: > > $ cat allrandomconfig > CONFIG_EXPERT=n > CONFIG_MY_CRITICAL_FEATURE=y > ... > $ > > and use "make randconfig KCONFIG_ALLCONFIG=1". Booting (truly) randconfig builds is like booting allyesconfig or allnoconfig builds: no one sane should do that, right? Paul Bolle -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/