public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Fernand Sieber <sieberf@amazon.com>
Cc: stable@vger.kernel.org, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH] KVM: x86/pmu: Do not accidentally create BTS events
Date: Mon, 1 Dec 2025 22:26:08 +0800	[thread overview]
Message-ID: <aS2lgKv0B5c9Av0l@656a63d76ae5> (raw)
In-Reply-To: <20251201142359.344741-1-sieberf@amazon.com>

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-1

Rule: add the tag "Cc: stable@vger.kernel.org" in the sign-off area to have the patch automatically included in the stable tree.
Subject: [PATCH] KVM: x86/pmu: Do not accidentally create BTS events
Link: https://lore.kernel.org/stable/20251201142359.344741-1-sieberf%40amazon.com

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki




  reply	other threads:[~2025-12-01 14:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-01 14:23 [PATCH] KVM: x86/pmu: Do not accidentally create BTS events Fernand Sieber
2025-12-01 14:26 ` kernel test robot [this message]
2025-12-01 14:45 ` Woodhouse, David
2025-12-02  9:35   ` Peter Zijlstra
2025-12-02  9:59     ` Fernand Sieber
2025-12-02 10:03 ` Peter Zijlstra
2025-12-02 12:44   ` Peter Zijlstra
2025-12-02 16:03     ` Sean Christopherson
2025-12-10 10:11     ` Fernand Sieber
2025-12-10 11:16       ` Peter Zijlstra
2025-12-11 18:36         ` [PATCH v2] perf/x86/intel: Do not enable BTS for guests Fernand Sieber
2025-12-11 18:38           ` kernel test robot
2026-01-14 17:25           ` David Woodhouse
2026-01-21 13:57             ` Fernand Sieber
2026-01-21 15:31               ` Peter Zijlstra
2026-01-21 15:50           ` [tip: perf/urgent] " tip-bot2 for Fernand Sieber

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=aS2lgKv0B5c9Av0l@656a63d76ae5 \
    --to=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=sieberf@amazon.com \
    --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