From: Ryan Roberts <ryan.roberts@arm.com>
To: kernel test robot <lkp@intel.com>
Cc: stable@vger.kernel.org, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH 6.16-6.17 2/2] arm64: errata: Apply workarounds for Neoverse-V3AE
Date: Mon, 20 Oct 2025 10:34:18 +0100 [thread overview]
Message-ID: <f3524b4c-f271-40ac-9038-c38c0bd07901@arm.com> (raw)
In-Reply-To: <aPYBJGWKS1hS5NFF@ff1a9926167f>
On 20/10/2025 10:30, kernel test robot wrote:
> Hi,
>
> Thanks for your patch.
>
> FYI: kernel test robot notices the stable kernel rule is not satisfied.
>
> The check is based on https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html#option-3
>
> Rule: The upstream commit ID must be specified with a separate line above the commit text.
> Subject: [PATCH 6.16-6.17 2/2] arm64: errata: Apply workarounds for Neoverse-V3AE
> Link: https://lore.kernel.org/stable/20251020092741.592431-3-ryan.roberts%40arm.com
>
> Please ignore this mail if the patch is not relevant for upstream.
>
Ugh, I re-backported this verion from mainline and forgot to re-add the extras
to the commit log. I'll resend the 6.16-617 series. Sorry about that...
prev parent reply other threads:[~2025-10-20 9:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-20 9:27 [PATCH 6.16-6.17 0/2] arm64: errata: Apply workarounds for Neoverse-V3AE Ryan Roberts
2025-10-20 9:27 ` [PATCH 6.16-6.17 1/2] arm64: cputype: Add Neoverse-V3AE definitions Ryan Roberts
2025-10-20 9:27 ` [PATCH 6.16-6.17 2/2] arm64: errata: Apply workarounds for Neoverse-V3AE Ryan Roberts
2025-10-20 9:30 ` kernel test robot
2025-10-20 9:34 ` 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=f3524b4c-f271-40ac-9038-c38c0bd07901@arm.com \
--to=ryan.roberts@arm.com \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=stable@vger.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