From: Ryan Roberts <ryan.roberts@arm.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, catalin.marinas@arm.com, will@kernel.org,
mark.rutland@arm.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5.4-6.17 0/2] arm64: errata: Apply workarounds for Neoverse-V3AE
Date: Mon, 20 Oct 2025 09:59:04 +0100 [thread overview]
Message-ID: <0e78a91d-f791-4cc2-be58-a44e2ec7e6f5@arm.com> (raw)
In-Reply-To: <2025101708-antsy-steadier-5ab6@gregkh>
On 17/10/2025 08:08, Greg KH wrote:
> On Thu, Oct 16, 2025 at 12:12:04PM +0100, Ryan Roberts wrote:
>> Hi All,
>>
>> This series is a backport intended for all supported stable kernels (5.4-6.17)
>> of the recent errata workarounds for Neoverse-V3AE, which were originally posted
>> at:
>>
>> https://lore.kernel.org/all/20250919145832.4035534-1-ryan.roberts@arm.com/
>>
>> ... and were originally merged upstream in v6.18-rc1.
>>
>> I've tested that these patches apply to 5.4-6.12 without issue, but there is a
>> trivial conflict to resolve in silicon-errata.rst for it to apply to 6.16 and
>> 6.17. Are you happy to deal with that or should I send a separate series?
>
> Please resend a separate series for that, and then resend this series as
> well, marked for the specific kernel releases that they are for.
OK will do. Incoming shortly...
>
> thanks,
>
> greg k-h
prev parent reply other threads:[~2025-10-20 8:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-16 11:12 Ryan Roberts
2025-10-16 11:12 ` [PATCH 5.4-6.17 1/2] arm64: cputype: Add Neoverse-V3AE definitions Ryan Roberts
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:08 ` [PATCH 5.4-6.17 0/2] " Greg KH
2025-10-20 8:59 ` Ryan Roberts [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=0e78a91d-f791-4cc2-be58-a44e2ec7e6f5@arm.com \
--to=ryan.roberts@arm.com \
--cc=catalin.marinas@arm.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=stable@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
all inboxes | Powered by JetHome®