From: John Garry <john.garry@huawei.com>
To: Anders Roxell <anders.roxell@linaro.org>, <catalin.marinas@arm.com>
Cc: <will@kernel.org>, <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm64: Kconfig: add a choice for endianess
Date: Tue, 12 Nov 2019 16:24:31 +0000 [thread overview]
Message-ID: <e44db1ec-e562-18c4-ca6f-96e4279564ed@huawei.com> (raw)
In-Reply-To: <20191112160144.8357-1-anders.roxell@linaro.org>
On 12/11/2019 16:01, Anders Roxell wrote:
> 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. Another concern that thas come up is that ACPI in't built
/s/wants/want/, s/thas/has/, s/in't/isn't/
> for an allmodconfig kernel today since that also depends on !CPU_BIG_ENDIAN.
>
> Rework so that we introduce a 'choice' and default the choice to
> CPU_LITTLE_ENDIAN. That means that when we build an allmodconfig kernel
> it will default to CPU_LITTLE_ENDIAN that most people tends to want.
>
> Signed-off-by: Anders Roxell <anders.roxell@linaro.org>
FWIW, apart from spelling mistakes:
Reviewed-by: John Garry <john.garry@huawei.com>
> ---
> arch/arm64/Kconfig | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
>
> diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
> index 64764ca92fca..62f83c234a61 100644
> --- a/arch/arm64/Kconfig
> +++ b/arch/arm64/Kconfig
> @@ -877,11 +877,24 @@ config ARM64_PA_BITS
> default 48 if ARM64_PA_BITS_48
> default 52 if ARM64_PA_BITS_52
>
> +choice
> + prompt "Endianess"
Should this be "Endianness"?
> + default CPU_LITTLE_ENDIAN
> + help
> + Choose what mode you plan on running your kernel in.
> +
> config CPU_BIG_ENDIAN
> bool "Build big-endian kernel"
> help
> Say Y if you plan on running a kernel in big-endian mode.
>
> +config CPU_LITTLE_ENDIAN
> + bool "Build little-endian kernel"
> + help
> + Say Y if you plan on running a kernel in little-endian mode.
> +
> +endchoice
> +
> config SCHED_MC
> bool "Multi-core scheduler support"
> help
>
next prev parent reply other threads:[~2019-11-12 16:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-12 16:01 [PATCH] arm64: Kconfig: add a choice for endianess Anders Roxell
2019-11-12 16:24 ` John Garry [this message]
2019-11-12 17:27 ` Will Deacon
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=e44db1ec-e562-18c4-ca6f-96e4279564ed@huawei.com \
--to=john.garry@huawei.com \
--cc=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