Hi Yann, On Thu, 8 Aug 2013 23:54:49 +0200 "Yann E. MORIN" <yann.morin.1998@xxxxxxx> wrote: > > Ok, I've had a look in the linux-next archives, and I think I got it. > Is the following right? > > git clean -d; git clean -dX # To be sure tree is clean > touch empty > make KCONFIG_ALLCONFIG=empty allmodconfig > grep MODULES .config > $ CONFIG_MODULES is not set Yes, that is what I am seeing. > If so, I think I found the reason: the modules symbol is _always_ set to > being valid as soon as KCONFIG_ALLCONFIG is read, even if it was not > present in that file. > > Since it is set to be valid, the following change means it is not > affected another value later on. > > So, I wonder what the best option is: > 1- revert the following, and find another solution, > 2- de-specialise the modules symbol, > 3- or further specialise the modules symbol. > > I'd be inclined to go for 1, but I have no straightforward idea so far. > It's late here, so I'll look more thouroughly this WE. Thanks. -- Cheers, Stephen Rothwell sfr@xxxxxxxxxxxxxxxx
Attachment:
pgpO5nmk6usOk.pgp
Description: PGP signature
