From: Catalin Marinas <catalin.marinas@arm.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [GIT PULL] arm64 post-Spectre BHB fix for 5.17
Date: Wed, 9 Mar 2022 22:29:25 +0000 [thread overview]
Message-ID: <YikqRdJFLdl8b6HG@arm.com> (raw)
Hi Linus,
Please pull the arm64 fix below. It's based onto the arm64 Spectre BHB
branch that was merged yesterday.
Thanks.
The following changes since commit 58c9a5060cb7cd529d49c93954cdafe81c1d642a:
arm64: proton-pack: Include unprivileged eBPF status in Spectre v2 mitigation reporting (2022-03-07 17:25:52 +0000)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux tags/arm64-fixes
for you to fetch changes up to 52c9f93a9c482251cb0d224faa602ba26d462be8:
arm64: Do not include __READ_ONCE() block in assembly files (2022-03-09 21:56:50 +0000)
----------------------------------------------------------------
Fix kernel build with clang LTO after the inclusion of the Spectre BHB
arm64 mitigations.
----------------------------------------------------------------
Nathan Chancellor (1):
arm64: Do not include __READ_ONCE() block in assembly files
arch/arm64/include/asm/rwonce.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--
Catalin
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2022-03-09 22:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 22:29 Catalin Marinas [this message]
2022-03-09 22:40 ` [GIT PULL] arm64 post-Spectre BHB fix for 5.17 pr-tracker-bot
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=YikqRdJFLdl8b6HG@arm.com \
--to=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--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).