Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: linux-arm-kernel@lists.infradead.org,
	Beata Michalska <beata.michalska@arm.com>
Cc: catalin.marinas@arm.com, mark.rutland@arm.com,
	kernel-team@android.com, Will Deacon <will@kernel.org>,
	Vladimir.Murzin@arm.com, suzuki.poulose@arm.com,
	James.Morse@arm.com, xuewen.yan94@gmail.com,
	seanwang1@lenovo.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/2] arm64: errata: Share broken AMU constant-counter handling
Date: Thu,  1 Oct 2026 16:50:42 +0100	[thread overview]
Message-ID: <179085736057.651403.12389463608357199980.b4-ty@kernel.org> (raw)
In-Reply-To: <20261001090050.3849551-1-beata.michalska@arm.com>

On Thu, 01 Oct 2026 11:00:30 +0200, Beata Michalska wrote:
> This series factors out the existing Cortex-A510 erratum 2457168 AMU constant
> counter workaround into a generic broken AMU constant-counter capability,
> then wires Cortex-A725 erratum 3821522 into the same handling.
> 

Applied to arm64 (for-next/fixes), thanks!

[1/2] arm64: errata: Factor out broken AMU const counter cap
      https://git.kernel.org/arm64/c/573371caf7ae
[2/2] arm64: errata: Add Cortex-A725 erratum 3821522 workaround
      https://git.kernel.org/arm64/c/45f730467987

Cheers,
-- 
Will

https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev


      parent reply	other threads:[~2026-10-01 15:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-01  9:00 [PATCH v4 0/2] arm64: errata: Share broken AMU constant-counter handling Beata Michalska
2026-10-01  9:00 ` [PATCH v4 1/2] arm64: errata: Factor out broken AMU const counter cap Beata Michalska
2026-10-01 12:10   ` Vladimir Murzin
2026-10-01  9:00 ` [PATCH v4 2/2] arm64: errata: Add Cortex-A725 erratum 3821522 workaround Beata Michalska
2026-10-01 12:12   ` Vladimir Murzin
2026-10-01 15:50 ` 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=179085736057.651403.12389463608357199980.b4-ty@kernel.org \
    --to=will@kernel.org \
    --cc=James.Morse@arm.com \
    --cc=Vladimir.Murzin@arm.com \
    --cc=beata.michalska@arm.com \
    --cc=catalin.marinas@arm.com \
    --cc=kernel-team@android.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=seanwang1@lenovo.com \
    --cc=suzuki.poulose@arm.com \
    --cc=xuewen.yan94@gmail.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