From: Sasha Levin <sashal@kernel.org>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: "Greg KH" <gregkh@linuxfoundation.org>,
"# 3.4.x" <stable@vger.kernel.org>,
clang-built-linux <clang-built-linux@googlegroups.com>,
"Masahiro Yamada" <masahiroy@kernel.org>,
"Russell King" <rmk+kernel@arm.linux.org.uk>,
"Dmitry Golovin" <dima@golovin.in>,
"Matthias Männich" <maennich@google.com>,
"Nathan Chancellor" <natechancellor@gmail.com>
Subject: Re: llvm-nm and lld patches for arm32
Date: Wed, 14 Oct 2020 10:00:46 -0400 [thread overview]
Message-ID: <20201014140046.GQ2415204@sasha-vm> (raw)
In-Reply-To: <CAKwvOdnBqCT0XG298nLqE7=WvxrYJFqV6jZ8-fZX0fF67bLQBQ@mail.gmail.com>
On Mon, Oct 12, 2020 at 03:32:46PM -0700, Nick Desaulniers wrote:
>Dear Stable Maintainers,
>Please consider cherry-picking:
>
>commit fe00e50b2db8 ("ARM: 8858/1: vdso: use $(LD) instead of $(CC) to
>link VDSO")
>
>to linux-4.19.y.
>
>It cherry picks cleanly and first landed in v5.2-rc1.
>
>It allows us to more easily use ld.lld on arm32 for Android.
>
>
>Also, please consider cherry-picking:
>
>commit 29c623d64f0d ("ARM: 8939/1: kbuild: use correct nm executable")
>
>to both linux-5.4.y and linux-4.19.y.
>
>It cherry picks cleanly and first landed in v5.5-rc1.
>
>It allows us to more easily use llvm-nm on arm32 for Android.
I've queued up the patches.
>I've attached both backports as mbox files. Please let me know if it
>would be preferable in the future for me to have one email per patch
>being backported. I tested both locally, and the patches are passing
>our presubmit testing in Android.
If the patches apply cleanly and pass your tests as-is, it's enough to
just list the commits and let us cherry pick. No need to attach the
patches to the mail.
--
Thanks,
Sasha
prev parent reply other threads:[~2020-10-14 14:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 22:32 llvm-nm and lld patches for arm32 Nick Desaulniers
2020-10-14 14:00 ` Sasha Levin [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=20201014140046.GQ2415204@sasha-vm \
--to=sashal@kernel.org \
--cc=clang-built-linux@googlegroups.com \
--cc=dima@golovin.in \
--cc=gregkh@linuxfoundation.org \
--cc=maennich@google.com \
--cc=masahiroy@kernel.org \
--cc=natechancellor@gmail.com \
--cc=ndesaulniers@google.com \
--cc=rmk+kernel@arm.linux.org.uk \
--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).