On Fri, May 22, 2015 at 9:41 AM, Borislav Petkov <b...@alien8.de> wrote:
>> 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".
>
> I do that but does everyone who builds randconfigs? I had to go and look
> what variables Kbuild honors and prep an all.config and yadda yadda...
The ones who just build them probably not (unless they care about a specific
case), which increases build coverage, so that's good.
The ones who boot them probably do, else they'll find out the hard way...
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
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/
