All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Bolle <pebolle@tiscali.nl>
To: Borislav Petkov <bp@alien8.de>
Cc: Ingo Molnar <mingo@kernel.org>, X86 ML <x86@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86/Kconfig: Fix allnoconfig without explicitly specified ARCH
Date: Fri, 03 Apr 2015 17:33:03 +0200	[thread overview]
Message-ID: <1428075183.2491.21.camel@tiscali.nl> (raw)
In-Reply-To: <20150403145950.GE3418@pd.tnic>

Borislav Petkov schreef op vr 03-04-2015 om 16:59 [+0200]:
> On Fri, Apr 03, 2015 at 03:42:18PM +0200, Paul Bolle wrote:
> > A side effect of this patch is that allnoconfig when building on 32 bits
> > now also requires to set ARCH=i386, which is surprising. This seems to
> 
> How else would you build a 32-bit allnoconfig?

Well, "when building on 32 bits" it currently suffices to do:
    make allnoconfig

and the patch changes that.

Just like it is surprising to get a CONFIG_X86_32=y .config when doing
allnoconfig on x86_64 it is also surprising to get a
CONFIG_X86_64=y .config when doing allyesconfig on i386. So I think a
more general solution to these surprising .configs should be considered.
 
Thanks,


Paul Bolle


  reply	other threads:[~2015-04-03 15:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-03 11:00 [PATCH] x86/Kconfig: Fix allnoconfig without explicitly specified ARCH Borislav Petkov
2015-04-03 13:42 ` Paul Bolle
2015-04-03 14:59   ` Borislav Petkov
2015-04-03 15:33     ` Paul Bolle [this message]
2015-04-03 17:23       ` Borislav Petkov
2015-04-03 21:43         ` Paul Bolle
2015-04-04  9:35           ` Ingo Molnar

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=1428075183.2491.21.camel@tiscali.nl \
    --to=pebolle@tiscali.nl \
    --cc=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=x86@kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.