From: Sasha Levin <sashal@kernel.org>
To: Mark Rutland <mark.rutland@arm.com>
Cc: stable@vger.kernel.org, anshuman.khandual@arm.com,
catalin.marinas@arm.com, james.morse@arm.com, will@kernel.org
Subject: Re: [PATCH 6.10.y 0/8] arm64: errata: Speculative SSBS workaround
Date: Mon, 12 Aug 2024 07:26:57 -0400 [thread overview]
Message-ID: <ZrnxgS9RTDP4FDtK@sashalap> (raw)
In-Reply-To: <20240809095120.3475335-1-mark.rutland@arm.com>
On Fri, Aug 09, 2024 at 10:51:12AM +0100, Mark Rutland wrote:
>Hi,
>
>This series is a v6.10-only backport (based on v6.10.3) of the upstream
>workaround for SSBS errata on Arm Ltd CPUs, as affected parts are likely to be
>used with stable kernels. This does not apply to earlier stable trees, which
>will receive a separate backport.
I've queued up the backports for the various versions, thanks!
--
Thanks,
Sasha
next prev parent reply other threads:[~2024-08-12 11:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-09 9:51 [PATCH 6.10.y 0/8] arm64: errata: Speculative SSBS workaround Mark Rutland
2024-08-09 9:51 ` [PATCH 6.10.y 1/8] arm64: cputype: Add Cortex-X3 definitions Mark Rutland
2024-08-09 9:51 ` [PATCH 6.10.y 2/8] arm64: cputype: Add Cortex-A720 definitions Mark Rutland
2024-08-09 9:51 ` [PATCH 6.10.y 3/8] arm64: cputype: Add Cortex-X925 definitions Mark Rutland
2024-08-09 9:51 ` [PATCH 6.10.y 4/8] arm64: errata: Unify speculative SSBS errata logic Mark Rutland
2024-08-09 9:51 ` [PATCH 6.10.y 5/8] arm64: errata: Expand speculative SSBS workaround Mark Rutland
2024-08-09 9:51 ` [PATCH 6.10.y 6/8] arm64: cputype: Add Cortex-X1C definitions Mark Rutland
2024-08-09 9:51 ` [PATCH 6.10.y 7/8] arm64: cputype: Add Cortex-A725 definitions Mark Rutland
2024-08-09 9:51 ` [PATCH 6.10.y 8/8] arm64: errata: Expand speculative SSBS workaround (again) Mark Rutland
2024-08-12 11:26 ` Sasha Levin [this message]
2024-08-12 11:31 ` [PATCH 6.10.y 0/8] arm64: errata: Speculative SSBS workaround Mark Rutland
2024-08-12 14:07 ` Greg KH
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=ZrnxgS9RTDP4FDtK@sashalap \
--to=sashal@kernel.org \
--cc=anshuman.khandual@arm.com \
--cc=catalin.marinas@arm.com \
--cc=james.morse@arm.com \
--cc=mark.rutland@arm.com \
--cc=stable@vger.kernel.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