From: Greg KH <greg@kroah.com>
To: Nanyong Sun <sunnanyong@huawei.com>
Cc: catalin.marinas@arm.com, will@kernel.org, suzuki.poulose@arm.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
james.morse@arm.com, hayashi.kunihiko@socionext.com
Subject: Re: [PATCH v4.4 v4.9 v4.14] arm64: Extend workaround for erratum 1024718 to all versions of Cortex-A55
Date: Mon, 4 Oct 2021 13:09:14 +0200 [thread overview]
Message-ID: <YVrg2mXyaI/5D6mH@kroah.com> (raw)
In-Reply-To: <20210929075210.819396-1-sunnanyong@huawei.com>
On Wed, Sep 29, 2021 at 03:52:10PM +0800, Nanyong Sun wrote:
> From: Suzuki K Poulose <suzuki.poulose@arm.com>
>
> commit c0b15c25d25171db4b70cc0b7dbc1130ee94017d upstream.
>
> The erratum 1024718 affects Cortex-A55 r0p0 to r2p0. However
> we apply the work around for r0p0 - r1p0. Unfortunately this
> won't be fixed for the future revisions for the CPU. Thus
> extend the work around for all versions of A55, to cover
> for r2p0 and any future revisions.
>
> Cc: stable@vger.kernel.org #v4.4 v4.9 v4.14
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Cc: Will Deacon <will@kernel.org>
> Cc: James Morse <james.morse@arm.com>
> Cc: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
> Signed-off-by: Suzuki K Poulose <suzuki.poulose@arm.com>
> Link: https://lore.kernel.org/r/20210203230057.3961239-1-suzuki.poulose@arm.com
> [will: Update Kconfig help text]
> Signed-off-by: Will Deacon <will@kernel.org>
> [Nanyon: adjust for stable version below v4.16, which set TCR_HD earlier
> in assembly code]
> Signed-off-by: Nanyong Sun <sunnanyong@huawei.com>
Now queued up,t hanks.
greg k-h
prev parent reply other threads:[~2021-10-04 11:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-29 7:52 [PATCH v4.4 v4.9 v4.14] arm64: Extend workaround for erratum 1024718 to all versions of Cortex-A55 Nanyong Sun
2021-10-04 11:09 ` 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=YVrg2mXyaI/5D6mH@kroah.com \
--to=greg@kroah.com \
--cc=catalin.marinas@arm.com \
--cc=hayashi.kunihiko@socionext.com \
--cc=james.morse@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=sunnanyong@huawei.com \
--cc=suzuki.poulose@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