mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	Michal Marek <mmarek@suse.cz>, Kevin Hilman <khilman@linaro.org>,
	sedat.dilek@gmail.com, "Theodore Ts'o" <tytso@mit.edu>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Linux kbuild ML <linux-kbuild@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the ext4 tree
Date: Fri, 9 Aug 2013 09:58:17 +1000	[thread overview]
Message-ID: <20130809095817.4fafdf8cb64428ea062a19b7@canb.auug.org.au> (raw)
In-Reply-To: <20130808215449.GD3282@free.fr>

[-- Attachment #1: Type: text/plain, Size: 1132 bytes --]

Hi Yann,

On Thu, 8 Aug 2013 23:54:49 +0200 "Yann E. MORIN" <yann.morin.1998@free.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@canb.auug.org.au

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2013-08-08 23:58 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-29  1:08 Stephen Rothwell
2013-07-31  1:27 ` Stephen Rothwell
2013-08-07  5:16 ` Sedat Dilek
2013-08-07  5:38   ` Stephen Rothwell
2013-08-07  5:43     ` Sedat Dilek
2013-08-07  5:59       ` Stephen Rothwell
2013-08-07 15:28     ` Kevin Hilman
2013-08-08  0:22       ` Stephen Rothwell
2013-08-08  0:36         ` Stephen Rothwell
2013-08-08 19:16           ` Yann E. MORIN
2013-08-08 21:54             ` Yann E. MORIN
2013-08-08 23:58               ` Stephen Rothwell [this message]
2013-08-09 11:42               ` Sam Ravnborg
2013-08-11 21:39                 ` Yann E. MORIN
2013-08-16 13:10                   ` Michal Marek
2013-08-16 17:14                     ` Sam Ravnborg
2013-08-16 18:02                       ` Yann E. MORIN
  -- strict thread matches above, loose matches on Subject: below --
2026-05-29 11:59 Mark Brown
2026-06-01 12:43 ` Mark Brown
2026-06-01 15:17   ` Guan-Chun Wu
2025-07-14 22:22 Stephen Rothwell
2025-07-15  3:31 ` Zhang Yi
2025-02-13 22:58 Stephen Rothwell
2018-10-08 23:51 Stephen Rothwell
2018-10-09  5:23 ` Theodore Y. Ts'o
2016-02-07 23:50 Stephen Rothwell
2016-01-03 23:34 Stephen Rothwell
2016-01-04 13:49 ` Theodore Ts'o
2015-07-23  0:56 Stephen Rothwell
2015-07-23 16:49 ` Theodore Ts'o
2015-07-23 17:23   ` Theodore Ts'o
2015-07-23 17:41     ` Tejun Heo
2015-05-07  1:14 Stephen Rothwell
2013-04-03 23:43 Stephen Rothwell
2013-04-04 13:18 ` Lukáš Czerner
2013-04-04 13:20   ` Theodore Ts'o
2013-04-04 13:27     ` Lukáš Czerner
2012-07-10  1:23 Stephen Rothwell
2012-07-10  1:48 ` Aditya Kali
2012-01-03  0:35 Stephen Rothwell
2012-01-05 21:06 ` Stephen Rothwell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130809095817.4fafdf8cb64428ea062a19b7@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=khilman@linaro.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mmarek@suse.cz \
    --cc=rostedt@goodmis.org \
    --cc=sedat.dilek@gmail.com \
    --cc=tytso@mit.edu \
    --cc=yann.morin.1998@free.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®