From: Will Deacon <will@kernel.org>
To: linux-kernel@vger.kernel.org,
Anshuman Khandual <anshuman.khandual@arm.com>,
catalin.marinas@arm.com, linux-arm-kernel@lists.infradead.org
Cc: kernel-team@android.com, Will Deacon <will@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
linux-doc@vger.kernel.org, James Morse <james.morse@arm.com>,
Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH V3 0/2] arm64: errata: Workaround Cortex-A715 errata #2645198
Date: Fri, 18 Nov 2022 19:40:40 +0000 [thread overview]
Message-ID: <166879036104.4045194.6085821745248609037.b4-ty@kernel.org> (raw)
In-Reply-To: <20221116140915.356601-1-anshuman.khandual@arm.com>
On Wed, 16 Nov 2022 19:39:13 +0530, Anshuman Khandual wrote:
> This series adds Cortex-A715 partnumber and workarounds the errata #2645198
> which gets triggered when an userspace page mapping permission changes from
> executable to non-executable, corrupting both ESR_EL1/FAR_EL1 registers
> when an instruction abort is taken.
>
> This series applies on v6.1-rc5.
>
> [...]
Applied to arm64 (for-next/errata), thanks!
[1/2] arm64: Add Cortex-715 CPU part definition
https://git.kernel.org/arm64/c/07e39e60bbf0
[2/2] arm64: errata: Workaround possible Cortex-A715 [ESR|FAR]_ELx corruption
https://git.kernel.org/arm64/c/44ecda71fd8a
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2022-11-18 19:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 14:09 Anshuman Khandual
2022-11-16 14:09 ` [PATCH V3 1/2] arm64: Add Cortex-715 CPU part definition Anshuman Khandual
2022-11-16 14:09 ` [PATCH V3 2/2] arm64: errata: Workaround possible Cortex-A715 [ESR|FAR]_ELx corruption Anshuman Khandual
2022-11-16 14:41 ` Catalin Marinas
2022-11-18 19:40 ` Will Deacon [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=166879036104.4045194.6085821745248609037.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=anshuman.khandual@arm.com \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=james.morse@arm.com \
--cc=kernel-team@android.com \
--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=suzuki.poulose@arm.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
all inboxes | Powered by JetHome®