All of lore.kernel.org
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: Will Deacon <will@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
	Ard Biesheuvel <ardb@kernel.org>,
	Eric Biggers <ebiggers@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	Alexei Starovoitov <ast@kernel.org>,
	Oliver Upton <oupton@kernel.org>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	Marc Zyngier <maz@kernel.org>
Subject: Re: [PATCH v3 12/13] arm64: Kbuild: Remove vestigial big-endian support
Date: Tue, 22 Sep 2026 16:17:35 +0100	[thread overview]
Message-ID: <arKcDyE6pkBI9YVt@arm.com> (raw)
In-Reply-To: <arKaWVwH5RXKpDTf@willie-the-truck>

On Tue, Sep 22, 2026 at 04:10:17PM +0100, Will Deacon wrote:
> On Mon, Sep 21, 2026 at 11:24:36AM +0100, Catalin Marinas wrote:
> > On Fri, Sep 18, 2026 at 03:52:14PM +0100, Will Deacon wrote:
> > > -choice
> > > -	prompt "Endianness"
> > > -	default CPU_LITTLE_ENDIAN
> > > -	help
> > > -	  Select the endianness of data accesses performed by the CPU. Userspace
> > > -	  applications will need to be compiled and linked for the endianness
> > > -	  that is selected here.
> > > -
> > > -config CPU_BIG_ENDIAN
> > > -	bool "Build big-endian kernel"
> > > -	depends on BROKEN
> > > -	help
> > > -	  Say Y if you plan on running a kernel with a big-endian userspace.
> > > -
> > > -config CPU_LITTLE_ENDIAN
> > > -	bool "Build little-endian kernel"
> > > -	help
> > > -	  Say Y if you plan on running a kernel with a little-endian userspace.
> > > -	  This is usually the case for distributions targeting arm64.
> > 
> > Running the checks through an LLM found that CONFIG_GVE depends on
> > X86 || CPU_LITTLE_ENDIAN, so it won't be enabled anymore.
> > 
> > I think that's the only positive test of CPU_LITTLE_ENDIAN.
> 
> Would you like me to add a '|| arm64' in there? I was a bit wary of doing
> so, given that I don't have a way to test it. Removing CPU_LITTLE_ENDIAN
> forces the issue, somewhat.

Or turn the dependency into X86 || !CPU_BIG_ENDIAN.

Was arm64 the only one to define CPU_LITTLE_ENDIAN before?

-- 
Catalin


  reply	other threads:[~2026-09-22 15:17 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-18 14:52 [PATCH v3 00/14] arm64: Remove unused big-endian support Will Deacon
2026-09-18 14:52 ` [PATCH v3 01/13] selftests/arm64: Remove " Will Deacon
2026-09-20 19:56   ` Thomas Gleixner
2026-09-18 14:52 ` [PATCH v3 02/13] arm64: bpf: Remove big-endian support from the JIT compiler Will Deacon
2026-09-18 14:52 ` [PATCH v3 03/13] arm64: crypto: Assume a little-endian kernel Will Deacon
2026-09-18 14:52 ` [PATCH v3 04/13] arm64: lib: Assume a little-endian kernel in custom library routines Will Deacon
2026-09-18 14:52 ` [PATCH v3 05/13] arm64: lib: Assume a little-endian kernel in optimised string routines Will Deacon
2026-09-18 14:52 ` [PATCH v3 06/13] arm64: assembler: Remove endianness helper macros Will Deacon
2026-09-18 14:52 ` [PATCH v3 07/13] arm64: vdso32: Always build compat vDSO object as little-endian Will Deacon
2026-09-18 14:52 ` [PATCH v3 08/13] KVM: arm64: Remove support for a big-endian hypervisor object Will Deacon
2026-09-18 14:52 ` [PATCH v3 09/13] arm64: Remove all usage of CONFIG_CPU_BIG_ENDIAN Will Deacon
2026-09-18 14:52 ` [PATCH v3 10/13] arm64: Remove all usage of __AARCH64EB__ Will Deacon
2026-09-18 14:52 ` [PATCH v3 11/13] crypto: hisilicon/sec2: Remove check of CONFIG_CPU_LITTLE_ENDIAN Will Deacon
2026-09-23  7:04   ` liulongfang
2026-09-18 14:52 ` [PATCH v3 12/13] arm64: Kbuild: Remove vestigial big-endian support Will Deacon
2026-09-21 10:24   ` Catalin Marinas
2026-09-22 15:10     ` Will Deacon
2026-09-22 15:17       ` Catalin Marinas [this message]
2026-09-22 15:32         ` Will Deacon
2026-09-18 14:52 ` [PATCH v3 13/13] drivers: Kconfig: Simplify dependencies on ARM64 && !CPU_BIG_ENDIAN Will Deacon
2026-09-18 16:22 ` [PATCH v3 00/14] arm64: Remove unused big-endian support Mark Rutland
2026-09-23 18:18 ` Catalin Marinas

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=arKcDyE6pkBI9YVt@arm.com \
    --to=catalin.marinas@arm.com \
    --cc=ardb@kernel.org \
    --cc=arnd@arndb.de \
    --cc=ast@kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=ebiggers@kernel.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maz@kernel.org \
    --cc=oupton@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 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.