Re: [GIT PULL] kconfig changes for v4.6-rc1

From: Geert Uytterhoeven
Date: Fri Mar 25 2016 - 05:03:48 EST


On Fri, Mar 25, 2016 at 9:54 AM, Geert Uytterhoeven
<geert@xxxxxxxxxxxxxx> wrote:
> On Thu, Mar 24, 2016 at 9:51 PM, Michal Marek <mmarek@xxxxxxx> wrote:
>> just two kconfig commits this time:
>> - kconfig Makefile fix for make 3.80
>> - Fix calculating symbols so that KCONFIG_ALLCONFIG=... does not disable
>> CONFIG_MODULES silently
>
>> for you to fetch changes up to 6b87b70c5339f30e3c5b32085e69625906513dc2:
>>
>> unbreak allmodconfig KCONFIG_ALLCONFIG=... (2016-02-01 15:12:40 +0100)
>>
>> ----------------------------------------------------------------
>> Al Viro (1):
>> unbreak allmodconfig KCONFIG_ALLCONFIG=...
>
> I can now indeed drop the
>
> CONFIG_MODULES=y
>
> line from my
>
> allmod.config
>
> However, this fix has the side-effect of enabling CONFIG_MODULES silently for
>
> make allyesconfig KCONFIG_ALLCONFIG=1
>
> Adding an explicit
>
> CONFIG_MODULES=n
>
> to the allyes.config file fixes that.
>
> IMHO CONFIG_MODULES should default to y when using allmodconfig, and
> default to n when using allyesconfig.

Hmm, it seems plain "make allyesconfig" also enables CONFIG_MODULES, and
makes many options modular. Is that intentional, especially the latter?

Gr{oetje,eeting}s,

Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx

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