public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: Borislav Petkov <bp@alien8.de>, X86 ML <x86@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86/Kconfig: Fix allnoconfig without explicitly specified ARCH
Date: Sat, 4 Apr 2015 11:35:25 +0200	[thread overview]
Message-ID: <20150404093525.GB20462@gmail.com> (raw)
In-Reply-To: <1428097434.7898.37.camel@x220>


* Paul Bolle <pebolle@tiscali.nl> wrote:

> On Fri, 2015-04-03 at 19:23 +0200, Borislav Petkov wrote:
> > On Fri, Apr 03, 2015 at 05:33:03PM +0200, Paul Bolle wrote:
> > > Well, "when building on 32 bits" it currently suffices to do:
> > >     make allnoconfig
> > > 
> > > and the patch changes that.
> > 
> > Hmm, so this would need more staring. The fact that 64-bit needs to set
> > CONFIG_64BIT, we would need a way to say:
> > 
> > 	option allnoconfig_y if ARCH = "x86"
> > 
> > And Kconfig doesn't support that yet...
> 
> The fact that "make allnoconfig" and "make allyesconfig" can give you
> a .config for another subarchitecture is annoying. [...]

Absolutely! No 'make *config' option should change the current 
.config's architecture, except if ARCH= is specified on the command 
line.

Thanks,

	Ingo

      reply	other threads:[~2015-04-04  9:35 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
2015-04-03 17:23       ` Borislav Petkov
2015-04-03 21:43         ` Paul Bolle
2015-04-04  9:35           ` Ingo Molnar [this message]

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=20150404093525.GB20462@gmail.com \
    --to=mingo@kernel.org \
    --cc=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pebolle@tiscali.nl \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox