From: Anders Roxell <anders.roxell@linaro.org>
To: catalin.marinas@arm.com, will@kernel.org
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Anders Roxell <anders.roxell@linaro.org>
Subject: [PATCH 3/3] arm64: configs: unset CPU_BIG_ENDIAN
Date: Thu, 26 Sep 2019 21:30:30 +0200 [thread overview]
Message-ID: <20190926193030.5843-5-anders.roxell@linaro.org> (raw)
In-Reply-To: <20190926193030.5843-1-anders.roxell@linaro.org>
When building allmodconfig KCONFIG_ALLCONFIG=$(pwd)/arch/arm64/configs/defconfig
CONFIG_CPU_BIG_ENDIAN gets enabled. Which tends not to be what most
people wants.
Rework so that we disable CONFIG_CPU_BIG_ENDIAN in the defcinfig file so
it doesn't get enabled when building allmodconfig kernels. When doing a
'make savedefconfig' CONFIG_CPU_BIG_ENDIAN will be dropped.
Signed-off-by: Anders Roxell <anders.roxell@linaro.org>
---
arch/arm64/configs/defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
index 878f379d8d84..c9aa6b9ee996 100644
--- a/arch/arm64/configs/defconfig
+++ b/arch/arm64/configs/defconfig
@@ -855,3 +855,4 @@ CONFIG_DEBUG_KERNEL=y
# CONFIG_SCHED_DEBUG is not set
CONFIG_MEMTEST=y
# CONFIG_CMDLINE_FORCE is not set
+# CONFIG_CPU_BIG_ENDIAN is not set
--
2.20.1
next prev parent reply other threads:[~2019-09-26 19:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-26 19:30 [PATCH 0/3] arm64: defconfig: set/unset for allmodconfig Anders Roxell
2019-09-26 19:30 ` [PATCH 1/3] arm64: configs: defconfig: enable DEBUG_PREEMPT and FTRACE Anders Roxell
2019-09-26 19:30 ` [PATCH] arm64: configs: defconfig: remove unneeded fragments Anders Roxell
2019-09-26 19:30 ` [PATCH 2/3] arm64: configs: unset CMDLINE_FORCE Anders Roxell
2019-10-15 8:38 ` John Garry
2019-09-26 19:30 ` Anders Roxell [this message]
2019-10-01 14:04 ` [PATCH 3/3] arm64: configs: unset CPU_BIG_ENDIAN John Garry
2019-10-03 7:40 ` Anders Roxell
2019-10-03 11:15 ` John Garry
2019-10-11 10:25 ` Arnd Bergmann
2019-10-11 10:27 ` Will Deacon
2019-10-11 10:33 ` Russell King - ARM Linux admin
2019-10-11 22:47 ` Arnd Bergmann
2019-10-12 14:50 ` Russell King - ARM Linux admin
2019-10-14 16:24 ` Will Deacon
2019-10-15 3:13 ` Hanjun Guo
2019-10-12 7:33 ` Hanjun Guo
2019-10-12 14:05 ` Arnd Bergmann
2019-10-14 6:12 ` Hanjun Guo
2019-10-14 16:20 ` Will Deacon
2019-10-14 10:58 ` [PATCH 0/3] arm64: defconfig: set/unset for allmodconfig John Garry
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=20190926193030.5843-5-anders.roxell@linaro.org \
--to=anders.roxell@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).