From: Borislav Petkov <bp@alien8.de>
To: Ingo Molnar <mingo@kernel.org>
Cc: X86 ML <x86@kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH] x86/Kconfig: Fix allnoconfig without explicitly specified ARCH
Date: Fri, 3 Apr 2015 13:00:28 +0200 [thread overview]
Message-ID: <1428058828-19302-1-git-send-email-bp@alien8.de> (raw)
From: Borislav Petkov <bp@suse.de>
Doing
$ make allnoconfig
I get a 32-bit allnoconfig:
$ grep -i x86 .config
# Linux/x86 4.0.0-rc6 Kernel Configuration
CONFIG_X86_32=y
CONFIG_X86=y
CONFIG_ARCH_DEFCONFIG="arch/x86/configs/i386_defconfig"
The same if I do:
$ make ARCH=i386 allnoconfig
$ grep -i x86 .config | head -20
CONFIG_X86_32=y
CONFIG_X86=y
CONFIG_ARCH_DEFCONFIG="arch/x86/configs/i386_defconfig"
Make allnoconfig without ARCH specified on the command line default to
64-bit.
Signed-off-by: Borislav Petkov <bp@suse.de>
---
arch/x86/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
index 0a37094e458e..04dfb4e7aeff 100644
--- a/arch/x86/Kconfig
+++ b/arch/x86/Kconfig
@@ -2,6 +2,7 @@
config 64BIT
bool "64-bit kernel" if ARCH = "x86"
default ARCH != "i386"
+ option allnoconfig_y
---help---
Say yes to build a 64-bit kernel - formerly known as x86_64
Say no to build a 32-bit kernel - formerly known as i386
--
2.3.3
next reply other threads:[~2015-04-03 11:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-03 11:00 Borislav Petkov [this message]
2015-04-03 13:42 ` [PATCH] x86/Kconfig: Fix allnoconfig without explicitly specified ARCH 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
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=1428058828-19302-1-git-send-email-bp@alien8.de \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox