From: Greg KH <gregkh@linuxfoundation.org>
To: catalin.marinas@arm.com, james.morse@arm.com,
linux-arm-kernel@lists.infradead.org, mark.rutland@arm.com,
ryan.roberts@arm.com, will@kernel.org
Cc: stable-commits@vger.kernel.org
Subject: Re: Patch "arm64: cputype: Add Neoverse-V3AE definitions" has been added to the 6.12-stable tree
Date: Fri, 17 Oct 2025 09:16:07 +0200 [thread overview]
Message-ID: <2025101749-gloomy-equipment-c4c3@gregkh> (raw)
In-Reply-To: <2025101719-lethargy-brunch-e56f@gregkh>
On Fri, Oct 17, 2025 at 09:13:19AM +0200, gregkh@linuxfoundation.org wrote:
>
> This is a note to let you know that I've just added the patch titled
>
> arm64: cputype: Add Neoverse-V3AE definitions
>
> to the 6.12-stable tree which can be found at:
> http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
>
> The filename of the patch is:
> arm64-cputype-add-neoverse-v3ae-definitions.patch
> and it can be found in the queue-6.12 subdirectory.
>
> If you, or anyone else, feels it should not be added to the stable tree,
> please let <stable@vger.kernel.org> know about it.
>
OOps, nope, dropping this one and the other one until we get a 6.17
version as well. Sorry for the noise.
greg k-h
next prev parent reply other threads:[~2025-10-17 7:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-16 11:12 [PATCH 5.4-6.17 0/2] arm64: errata: Apply workarounds for Neoverse-V3AE Ryan Roberts
2025-10-16 11:12 ` [PATCH 5.4-6.17 1/2] arm64: cputype: Add Neoverse-V3AE definitions Ryan Roberts
2025-10-17 7:13 ` Patch "arm64: cputype: Add Neoverse-V3AE definitions" has been added to the 6.12-stable tree gregkh
2025-10-17 7:16 ` Greg KH [this message]
2025-10-16 11:12 ` [PATCH 5.4-6.17 2/2] arm64: errata: Apply workarounds for Neoverse-V3AE Ryan Roberts
2025-10-17 7:13 ` Patch "arm64: errata: Apply workarounds for Neoverse-V3AE" has been added to the 6.12-stable tree gregkh
2025-10-17 7:08 ` [PATCH 5.4-6.17 0/2] arm64: errata: Apply workarounds for Neoverse-V3AE Greg KH
2025-10-20 8:59 ` Ryan Roberts
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=2025101749-gloomy-equipment-c4c3@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=catalin.marinas@arm.com \
--cc=james.morse@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=ryan.roberts@arm.com \
--cc=stable-commits@vger.kernel.org \
--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