From: Oliver Upton <oliver.upton@linux.dev>
To: D Scott Phillips <scott@os.amperecomputing.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
Mark Rutland <mark.rutland@arm.com>,
Anshuman Khandual <anshuman.khandual@arm.com>,
linux-arm-kernel@lists.infradead.org, linux-doc@vger.kernel.org,
Besar Wicaksono <bwicaksono@nvidia.com>,
Easwar Hariharan <eahariha@linux.microsoft.com>,
Rob Herring <robh@kernel.org>,
Andre Przywara <andre.przywara@arm.com>,
linux-kernel@vger.kernel.org, patches@amperecomputing.com,
Marc Zyngier <maz@kernel.org>,
kvmarm@lists.linux.dev, James Morse <james.morse@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>
Subject: Re: [PATCH v2] arm64: errata: Enable the AC03_CPU_38 workaround for ampere1a
Date: Wed, 28 Aug 2024 20:21:22 +0000 [thread overview]
Message-ID: <Zs-GwkIMauATQ16A@linux.dev> (raw)
In-Reply-To: <20240827211701.2216719-1-scott@os.amperecomputing.com>
On Tue, Aug 27, 2024 at 02:17:01PM -0700, D Scott Phillips wrote:
> The ampere1a cpu is affected by erratum AC04_CPU_10 which is the same
> bug as AC03_CPU_38. Add ampere1a to the AC03_CPU_38 workaround midr list.
>
> Signed-off-by: D Scott Phillips <scott@os.amperecomputing.com>
You'll probably want to cc this to stable, that can be handled when the
patch is applied though.
Acked-by: Oliver Upton <oliver.upton@linux.dev>
--
Thanks,
Oliver
next prev parent reply other threads:[~2024-08-28 20:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-27 21:17 [PATCH v2] arm64: errata: Enable the AC03_CPU_38 workaround for ampere1a D Scott Phillips
2024-08-28 20:21 ` Oliver Upton [this message]
2024-08-30 16:12 ` Will Deacon
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=Zs-GwkIMauATQ16A@linux.dev \
--to=oliver.upton@linux.dev \
--cc=andre.przywara@arm.com \
--cc=anshuman.khandual@arm.com \
--cc=bwicaksono@nvidia.com \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=eahariha@linux.microsoft.com \
--cc=james.morse@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=patches@amperecomputing.com \
--cc=robh@kernel.org \
--cc=scott@os.amperecomputing.com \
--cc=suzuki.poulose@arm.com \
--cc=will@kernel.org \
--cc=yuzenghui@huawei.com \
/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).