From: Catalin Marinas <catalin.marinas@arm.com>
To: linux-arm-kernel@lists.infradead.org,
Anshuman Khandual <anshuman.khandual@arm.com>
Cc: Will Deacon <will@kernel.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
linux-kernel@vger.kernel.org,
Suzuki Poulose <suzuki.poulose@arm.com>,
coresight@lists.linaro.org
Subject: Re: [PATCH V2 0/2] coresight: trbe: Update existing errata for Cortex-X2
Date: Mon, 24 Jan 2022 15:10:08 +0000 [thread overview]
Message-ID: <164303699846.16509.8389008992406508241.b4-ty@arm.com> (raw)
In-Reply-To: <1642994138-25887-1-git-send-email-anshuman.khandual@arm.com>
On Mon, 24 Jan 2022 08:45:36 +0530, Anshuman Khandual wrote:
> Errata ARM64_ERRATUM_[2119858|2224489] also affect some Cortex-X2 ranges as
> well. This series updates the errata definition and detection as required.
> This series applies on v5.17-rc1.
>
> Relevant identification document can be found here.
>
> https://developer.arm.com/documentation/101803/0200/AArch64-system-registers/
> AArch64-identification-register-summary/MIDR-EL1--Main-ID-Register
>
> [...]
Applied to arm64 (for-next/fixes), thanks!
[1/2] arm64: Add Cortex-X2 CPU part definition
https://git.kernel.org/arm64/c/72bb9dcb6c33
[2/2] arm64: errata: Update ARM64_ERRATUM_[2119858|2224489] with Cortex-X2 ranges
https://git.kernel.org/arm64/c/eb30d838a44c
--
Catalin
prev parent reply other threads:[~2022-01-24 15:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 3:15 Anshuman Khandual
2022-01-24 3:15 ` [PATCH V2 1/2] arm64: Add Cortex-X2 CPU part definition Anshuman Khandual
2022-01-24 3:15 ` [PATCH V2 2/2] arm64: errata: Update ARM64_ERRATUM_[2119858|2224489] with Cortex-X2 ranges Anshuman Khandual
2022-01-24 10:37 ` [PATCH V2 0/2] coresight: trbe: Update existing errata for Cortex-X2 Suzuki K Poulose
2022-01-24 15:10 ` Catalin Marinas [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=164303699846.16509.8389008992406508241.b4-ty@arm.com \
--to=catalin.marinas@arm.com \
--cc=anshuman.khandual@arm.com \
--cc=coresight@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--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
all inboxes | Powered by JetHome®