From: Greg KH <gregkh@linuxfoundation.org>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: Sasha Levin <sashal@kernel.org>,
"# 3.4.x" <stable@vger.kernel.org>, Will Deacon <will@kernel.org>,
Sami Tolvanen <samitolvanen@google.com>,
Andrew Murray <andrew.murray@arm.com>,
Jian Cai <jiancai@google.com>,
clang-built-linux <clang-built-linux@googlegroups.com>,
Kees Cook <keescook@chromium.org>,
Vincenzo Frascino <vincenzo.frascino@arm.com>,
Amit Daniel Kachhap <Amit.Kachhap@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>
Subject: Re: arm64 v4.19.y LLVM_IAS=y patches
Date: Sat, 19 Dec 2020 13:44:09 +0100 [thread overview]
Message-ID: <X931mZNdiLxCfEUy@kroah.com> (raw)
In-Reply-To: <CAKwvOdmEcjjw78K0Avj-7s5BBXcT7ARhEMMEYqpCP-ZT=2dAJw@mail.gmail.com>
On Mon, Dec 14, 2020 at 05:08:38PM -0800, Nick Desaulniers wrote:
> Dear stable kernel maintainers,
> Please consider applying the following backports of commit
> e0d5896bd356 ("arm64: lse: fix LSE atomics with LLVM's integrated
> assembler") which first landed in v5.6-rc1 and was already picked up
> into linux-5.4.y as f68668292496 in v5.4.22 (adjusted for a conflict
> due to commit addfc38672c7 ("arm64: atomics: avoid out-of-line ll/sc
> atomics") which landed in v5.4-rc1).
>
> Also contains a fix for that first patch which cherry-picks cleanly,
> commit dd1f6308b28e ("arm64: lse: Fix LSE atomics with LLVM").
>
> The attached patches allow for Android and CrOS to build with
> LLVM_IAS=1 for arm64 for v4.19.y (modulo one small patch that I will
> send tomorrow).
Now queued up, thanks.
greg k-h
prev parent reply other threads:[~2020-12-19 12:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-15 1:08 arm64 v4.19.y LLVM_IAS=y patches Nick Desaulniers
2020-12-19 12:44 ` Greg KH [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=X931mZNdiLxCfEUy@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Amit.Kachhap@arm.com \
--cc=andrew.murray@arm.com \
--cc=catalin.marinas@arm.com \
--cc=clang-built-linux@googlegroups.com \
--cc=jiancai@google.com \
--cc=keescook@chromium.org \
--cc=ndesaulniers@google.com \
--cc=samitolvanen@google.com \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=vincenzo.frascino@arm.com \
--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).