From: Linu Cherian <linu.cherian@arm.com>
To: Suzuki K Poulose <suzuki.poulose@arm.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Ryan Roberts <ryan.roberts@arm.com>,
Kevin Brodsky <kevin.brodsky@arm.com>,
Anshuman Khandual <anshuman.khandual@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] Add BBML3 cpu feature
Date: Fri, 3 Jul 2026 08:46:57 +0530 [thread overview]
Message-ID: <akcpqX8gpduwqtOg@a079125.arm.com> (raw)
In-Reply-To: <830a4d39-c829-4e79-a0ec-5a3633b58aa6@arm.com>
Hi Suzuki,
On Wed, Jul 01, 2026 at 11:11:35AM +0100, Suzuki K Poulose wrote:
> On 01/07/2026 10:41, Linu Cherian wrote:
> > Patches 1 and 2 introduces BBML3 cpu feature
> > Patches 3, 4 and 5 adds more cpus to the BBML3 support list,
> > which dont advertise themselves through the standard
> > MMFR2_ID registers.
> >
> > Linu Cherian (5):
> > arm64: cpufeature: Add BBML3
> > arm64: cpufeature: Detect BBML3 based on MMFR2 ID
>
>
> > arm64: cputype: Add Cortex-A520AE definitions
> > arm64: cputype: Add C1-Nano definitions
> > arm64: cpufeature: Extend bbml3 support list
>
> If you could move the last 3 patches to the top, would be easier
> for people to back port the "enable" BBLM3 for those CPUs, without
> the renaming conflicts.
>
IMHO, if we change the order, "arm64: cpufeature: Extend bbml3 support list"
title need to be tweaked and might not go well with this BBML3 support series.
Also, backporting issue wouldnt be a problem if the whole series is
backported and not just 3 patches in isolation ?
Thanks,
Linu Cherian.
next prev parent reply other threads:[~2026-07-03 3:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-01 9:41 [PATCH 0/5] Add BBML3 cpu feature Linu Cherian
2026-07-01 9:41 ` [PATCH 1/5] arm64: cpufeature: Add BBML3 Linu Cherian
2026-07-01 9:41 ` [PATCH 2/5] arm64: cpufeature: Detect BBML3 based on MMFR2 ID Linu Cherian
2026-07-02 10:45 ` Mark Rutland
2026-07-03 3:06 ` Linu Cherian
2026-07-03 4:36 ` Anshuman Khandual
2026-07-01 9:41 ` [PATCH 3/5] arm64: cputype: Add Cortex-A520AE definitions Linu Cherian
2026-07-03 5:07 ` Anshuman Khandual
2026-07-01 9:41 ` [PATCH 4/5] arm64: cputype: Add C1-Nano definitions Linu Cherian
2026-07-03 5:10 ` Anshuman Khandual
2026-07-01 9:41 ` [PATCH 5/5] arm64: cpufeature: Extend bbml3 support list Linu Cherian
2026-07-02 10:47 ` Mark Rutland
2026-07-03 3:03 ` Linu Cherian
2026-07-01 10:11 ` [PATCH 0/5] Add BBML3 cpu feature Suzuki K Poulose
2026-07-03 3:16 ` Linu Cherian [this message]
2026-07-03 4:15 ` Linu Cherian
2026-07-03 4:42 ` Anshuman Khandual
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=akcpqX8gpduwqtOg@a079125.arm.com \
--to=linu.cherian@arm.com \
--cc=anshuman.khandual@arm.com \
--cc=catalin.marinas@arm.com \
--cc=kevin.brodsky@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 \
--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