[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 9 Aug 2013 09:58:17 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: "Yann E. MORIN" <yann.morin.1998@...e.fr>
Cc: Steven Rostedt <rostedt@...dmis.org>,
Michal Marek <mmarek@...e.cz>,
Kevin Hilman <khilman@...aro.org>, sedat.dilek@...il.com,
Theodore Ts'o <tytso@....edu>, linux-next@...r.kernel.org,
linux-kernel@...r.kernel.org,
Linux kbuild ML <linux-kbuild@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the ext4 tree
Hi Yann,
On Thu, 8 Aug 2013 23:54:49 +0200 "Yann E. MORIN" <yann.morin.1998@...e.fr> 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@...b.auug.org.au
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists