From: kernel test robot <lkp@intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: stable@vger.kernel.org, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH 6.12 v2 3/8] KVM: arm64: Remove host FPSIMD saving for non-protected KVM
Date: Fri, 21 Mar 2025 08:15:29 +0800 [thread overview]
Message-ID: <Z9yvoefQbnQxbOjT@b424d92f189e> (raw)
In-Reply-To: <20250321-stable-sve-6-12-v2-3-417ca2278d18@kernel.org>
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.12 v2 3/8] KVM: arm64: Remove host FPSIMD saving for non-protected KVM
Link: https://lore.kernel.org/stable/20250321-stable-sve-6-12-v2-3-417ca2278d18%40kernel.org
Please ignore this mail if the patch is not relevant for upstream.
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-03-21 0:15 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-21 0:12 [PATCH 6.12 v2 0/8] KVM: arm64: Backport of SVE fixes to v6.12 Mark Brown
2025-03-21 0:12 ` [PATCH 6.12 v2 1/8] KVM: arm64: Calculate cptr_el2 traps on activating traps Mark Brown
2025-03-21 17:28 ` Sasha Levin
2025-03-24 18:59 ` Patch "KVM: arm64: Calculate cptr_el2 traps on activating traps" has been added to the 6.12-stable tree gregkh
2025-03-21 0:12 ` [PATCH 6.12 v2 2/8] KVM: arm64: Unconditionally save+flush host FPSIMD/SVE/SME state Mark Brown
2025-03-21 17:27 ` Sasha Levin
2025-03-24 18:59 ` Patch "KVM: arm64: Unconditionally save+flush host FPSIMD/SVE/SME state" has been added to the 6.12-stable tree gregkh
2025-03-21 0:12 ` [PATCH 6.12 v2 3/8] KVM: arm64: Remove host FPSIMD saving for non-protected KVM Mark Brown
2025-03-21 0:15 ` kernel test robot [this message]
2025-03-21 0:21 ` Mark Brown
2025-03-21 17:26 ` Sasha Levin
2025-03-24 18:59 ` Patch "KVM: arm64: Remove host FPSIMD saving for non-protected KVM" has been added to the 6.12-stable tree gregkh
2025-03-21 0:13 ` [PATCH 6.12 v2 4/8] KVM: arm64: Remove VHE host restore of CPACR_EL1.ZEN Mark Brown
2025-03-21 17:26 ` Sasha Levin
2025-03-24 18:59 ` Patch "KVM: arm64: Remove VHE host restore of CPACR_EL1.ZEN" has been added to the 6.12-stable tree gregkh
2025-03-21 0:13 ` [PATCH 6.12 v2 5/8] KVM: arm64: Remove VHE host restore of CPACR_EL1.SMEN Mark Brown
2025-03-21 17:29 ` Sasha Levin
2025-03-24 18:59 ` Patch "KVM: arm64: Remove VHE host restore of CPACR_EL1.SMEN" has been added to the 6.12-stable tree gregkh
2025-03-21 0:13 ` [PATCH 6.12 v2 6/8] KVM: arm64: Refactor exit handlers Mark Brown
2025-03-21 17:25 ` Sasha Levin
2025-03-24 18:59 ` Patch "KVM: arm64: Refactor exit handlers" has been added to the 6.12-stable tree gregkh
2025-03-21 0:13 ` [PATCH 6.12 v2 7/8] KVM: arm64: Mark some header functions as inline Mark Brown
2025-03-21 17:27 ` Sasha Levin
2025-03-24 18:59 ` Patch "KVM: arm64: Mark some header functions as inline" has been added to the 6.12-stable tree gregkh
2025-03-21 0:13 ` [PATCH 6.12 v2 8/8] KVM: arm64: Eagerly switch ZCR_EL{1,2} Mark Brown
2025-03-21 17:29 ` Sasha Levin
2025-03-24 18:59 ` Patch "KVM: arm64: Eagerly switch ZCR_EL{1,2}" has been added to the 6.12-stable tree gregkh
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=Z9yvoefQbnQxbOjT@b424d92f189e \
--to=lkp@intel.com \
--cc=broonie@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.