From: Will Deacon <will@kernel.org>
To: Catalin Marinas <catalin.marinas@arm.com>,
Ryan Roberts <ryan.roberts@arm.com>,
Kevin Brodsky <kevin.brodsky@arm.com>,
Anshuman Khandual <anshuman.khandual@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Linu Cherian <linu.cherian@arm.com>
Cc: kernel-team@android.com, Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/6] Add BBML3 cpu feature
Date: Thu, 6 Aug 2026 18:11:40 +0100 [thread overview]
Message-ID: <178601813324.394484.11007174313054248496.b4-ty@kernel.org> (raw)
In-Reply-To: <20260723044034.2983651-1-linu.cherian@arm.com>
On Thu, 23 Jul 2026 10:10:27 +0530, Linu Cherian wrote:
> - Patches 1, 2 and 3 adds more cpus to the bbml2_noabort
> support list. bbml2_noabort would eventually gets renamed
> to bbml3 in a subsequent patch as they are functionally
> equivalent.
> - Patches 4, 5 & 6 introduces BBML3 cpu feature
>
> Changelog from v3:
> * In order to cover future C1-Ultra and C1-Premium cpus starting
> from r1p1, replaced MIDR_REV_RANGE with MIDR_RANGE in patch 3
>
> [...]
Applied to arm64 (for-next/cpufeature), thanks!
[1/6] arm64: cputype: Add Cortex-A520AE definitions
https://git.kernel.org/arm64/c/482145e0327f
[2/6] arm64: cputype: Add C1-Nano definitions
https://git.kernel.org/arm64/c/357230cb5276
[3/6] arm64: cpufeature: Extend bbml2_noabort support list
https://git.kernel.org/arm64/c/a7ac60414475
[4/6] arm64: sysreg: Add BBM_3
https://git.kernel.org/arm64/c/e4fa24624308
[5/6] arm64: cpufeature: Rename BBML2_NOABORT as BBML3
https://git.kernel.org/arm64/c/94104e3cfa80
[6/6] arm64: cpufeature: Detect BBML3 based on ID_AA64MMFR2_EL1.BBM
https://git.kernel.org/arm64/c/879aca5119cd
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2026-08-06 17:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-23 4:40 [PATCH v4 0/6] Add BBML3 cpu feature Linu Cherian
2026-07-23 4:40 ` [PATCH v4 1/6] arm64: cputype: Add Cortex-A520AE definitions Linu Cherian
2026-07-23 4:40 ` [PATCH v4 2/6] arm64: cputype: Add C1-Nano definitions Linu Cherian
2026-07-23 4:40 ` [PATCH v4 3/6] arm64: cpufeature: Extend bbml2_noabort support list Linu Cherian
2026-07-23 7:26 ` Anshuman Khandual
2026-07-23 4:40 ` [PATCH v4 4/6] arm64: sysreg: Add BBM_3 Linu Cherian
2026-07-23 4:40 ` [PATCH v4 5/6] arm64: cpufeature: Rename BBML2_NOABORT as BBML3 Linu Cherian
2026-08-06 17:11 ` Will Deacon
2026-07-23 4:40 ` [PATCH v4 6/6] arm64: cpufeature: Detect BBML3 based on ID_AA64MMFR2_EL1.BBM Linu Cherian
2026-07-31 15:13 ` Will Deacon
2026-08-03 3:52 ` Linu Cherian
2026-08-03 4:19 ` Anshuman Khandual
2026-08-04 13:51 ` Will Deacon
2026-08-05 9:20 ` Linu Cherian
2026-08-06 11:26 ` Will Deacon
2026-08-06 17:11 ` 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=178601813324.394484.11007174313054248496.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=anshuman.khandual@arm.com \
--cc=catalin.marinas@arm.com \
--cc=kernel-team@android.com \
--cc=kevin.brodsky@arm.com \
--cc=linu.cherian@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=ryan.roberts@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