At Fri, 22 May 2015 10:17:48 +0200, Paul Bolle wrote: > > On Fri, 2015-05-22 at 09:11 +0200, Geert Uytterhoeven wrote: > > On Fri, May 22, 2015 at 8:53 AM, Borislav Petkov <b...@alien8.de> 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.)
But FW_LOADER is a tristate, so it might be inconsistent if selected randomly? Luis' patch doesn't add depends but just removes select. Takashi -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
