From: Will Deacon <will.deacon@arm.com>
To: Paul Kocialkowski <contact@paulk.fr>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Catalin Marinas <catalin.marinas@arm.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] arm64: Use aarch64elf and aarch64elfb emulation mode variants
Date: Mon, 2 Jul 2018 11:34:29 +0100 [thread overview]
Message-ID: <20180702103429.GC28665@arm.com> (raw)
In-Reply-To: <20180702091659.17571-1-contact@paulk.fr>
On Mon, Jul 02, 2018 at 11:16:59AM +0200, Paul Kocialkowski wrote:
> The aarch64linux and aarch64linuxb emulation modes are not supported by
> bare-metal toolchains and Linux using them forbids building the kernel
> with these toolchains.
>
> Since there is apparently no reason to target these emulation modes, the
> more generic elf modes are used instead, allowing to build on bare-metal
> toolchains as well as the already-supported ones.
>
> Fixes: 3d6a7b99e3fa ("arm64: ensure the kernel is compiled for LP64")
>
> Cc: stable@vger.kernel.org
> Signed-off-by: Paul Kocialkowski <contact@paulk.fr>
> ---
> arch/arm64/Makefile | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm64/Makefile b/arch/arm64/Makefile
> index 87f7d2f9f17c..3e959ac43b40 100644
> --- a/arch/arm64/Makefile
> +++ b/arch/arm64/Makefile
> @@ -67,14 +67,14 @@ KBUILD_CPPFLAGS += -mbig-endian
> CHECKFLAGS += -D__AARCH64EB__
> AS += -EB
> LD += -EB
> -LDFLAGS += -maarch64linuxb
> +LDFLAGS += -maarch64elfb
> UTS_MACHINE := aarch64_be
> else
> KBUILD_CPPFLAGS += -mlittle-endian
> CHECKFLAGS += -D__AARCH64EL__
> AS += -EL
> LD += -EL
> -LDFLAGS += -maarch64linux
> +LDFLAGS += -maarch64elf
> UTS_MACHINE := aarch64
> endif
Acked-by: Will Deacon <will.deacon@arm.com>
Will
prev parent reply other threads:[~2018-07-02 10:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-02 9:16 [PATCH] arm64: Use aarch64elf and aarch64elfb emulation mode variants Paul Kocialkowski
2018-07-02 10:34 ` Will Deacon [this message]
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=20180702103429.GC28665@arm.com \
--to=will.deacon@arm.com \
--cc=catalin.marinas@arm.com \
--cc=contact@paulk.fr \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.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).