From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jisheng Zhang <Jisheng.Zhang@synaptics.com>
Cc: "Nick Desaulniers" <ndesaulniers@google.com>,
stable@vger.kernel.org,
"Nathan Chancellor" <natechancellor@gmail.com>,
"Ard Biesheuvel" <ardb@kernel.org>,
"Sami Tolvanen" <samitolvanen@google.com>,
"Masahiro Yamada" <masahiroy@kernel.org>,
"Sedat Dilek" <sedat.dilek@gmail.com>,
"Thomas Bogendoerfer" <tsbogend@alpha.franken.de>,
"Catalin Marinas" <catalin.marinas@arm.com>,
"Will Deacon" <will@kernel.org>, "Alan Modra" <amodra@gmail.com>,
"Fāng-ruì Sòng" <maskray@google.com>,
"Quentin Perret" <qperret@google.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH stable-v5.4 v2 0/2] properly cope with -z norelro
Date: Fri, 25 Jun 2021 12:16:25 +0200 [thread overview]
Message-ID: <YNWs+X0DMKJIN+LD@kroah.com> (raw)
In-Reply-To: <20210625154737.3d64a434@xhacker.debian>
On Fri, Jun 25, 2021 at 03:47:37PM +0800, Jisheng Zhang wrote:
> Fix below build warning:
> aarch64-linux-gnu-ld: warning: -z norelro ignored
>
> Since v1
> - Backport a preparation patch as pointed out by Nick Desaulniers
>
> Nick Desaulniers (1):
> arm64: link with -z norelro for LLD or aarch64-elf
>
> Sami Tolvanen (1):
> kbuild: add CONFIG_LD_IS_LLD
>
> arch/arm64/Makefile | 10 +++++++---
> init/Kconfig | 3 +++
> 2 files changed, 10 insertions(+), 3 deletions(-)
>
> --
> 2.32.0
>
Took this series instead, thanks.
greg k-h
prev parent reply other threads:[~2021-06-25 10:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-25 7:47 [PATCH stable-v5.4 v2 0/2] properly cope with -z norelro Jisheng Zhang
2021-06-25 7:48 ` [PATCH stable-v5.4 v2 1/2] kbuild: add CONFIG_LD_IS_LLD Jisheng Zhang
2021-06-25 7:50 ` [PATCH stable-v5.4 v2 2/2] arm64: link with -z norelro for LLD or aarch64-elf Jisheng Zhang
2021-06-25 10:16 ` Greg Kroah-Hartman [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=YNWs+X0DMKJIN+LD@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Jisheng.Zhang@synaptics.com \
--cc=amodra@gmail.com \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=masahiroy@kernel.org \
--cc=maskray@google.com \
--cc=natechancellor@gmail.com \
--cc=ndesaulniers@google.com \
--cc=qperret@google.com \
--cc=samitolvanen@google.com \
--cc=sedat.dilek@gmail.com \
--cc=stable@vger.kernel.org \
--cc=tsbogend@alpha.franken.de \
--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