From: Hanjun Guo <guohanjun@huawei.com>
To: Will Deacon <will@kernel.org>, Arnd Bergmann <arnd@arndb.de>
Cc: Anders Roxell <anders.roxell@linaro.org>,
Catalin Marinas <catalin.marinas@arm.com>,
John Garry <john.garry@huawei.com>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
Olof Johansson <olof@lixom.net>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 3/3] arm64: configs: unset CPU_BIG_ENDIAN
Date: Sat, 12 Oct 2019 15:33:37 +0800 [thread overview]
Message-ID: <73701e9f-bee1-7ae8-2277-7a3576171cd4@huawei.com> (raw)
In-Reply-To: <20191011102747.lpbaur2e4nqyf7sw@willie-the-truck>
On 2019/10/11 18:27, Will Deacon wrote:
[...]
>
> Does anybody use BIG_ENDIAN? If we're not even building it then maybe we
> should get rid of it altogether on arm64. I don't know of any supported
> userspace that supports it or any CPUs that are unable to run little-endian
> binaries.
FWIW, massive telecommunication products (based on ARM64) form Huawei are using
BIG_ENDIAN, and will use BIG_ENDIAN in the near future as well.
Thanks
Hanjun
next prev parent reply other threads:[~2019-10-12 7:33 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 ` [PATCH 3/3] arm64: configs: unset CPU_BIG_ENDIAN Anders Roxell
2019-10-01 14:04 ` 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 [this message]
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=73701e9f-bee1-7ae8-2277-7a3576171cd4@huawei.com \
--to=guohanjun@huawei.com \
--cc=anders.roxell@linaro.org \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=john.garry@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--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).