From: kernel test robot <lkp@intel.com>
To: Len Brown <lenb@kernel.org>
Cc: stable@vger.kernel.org, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH backport to 6.10] x86/cpu: Add INTEL_FAM6_LUNARLAKE_M to X86_BUG_MONITOR
Date: Fri, 8 Nov 2024 21:53:54 +0800 [thread overview]
Message-ID: <Zy4X8lbLTKZlxOkH@0408e98e3aed> (raw)
In-Reply-To: <20241108135206.435793-2-lenb@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 backport to 6.10] x86/cpu: Add INTEL_FAM6_LUNARLAKE_M to X86_BUG_MONITOR
Link: https://lore.kernel.org/stable/20241108135206.435793-2-lenb%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:[~2024-11-08 13:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241108135206.435793-1-lenb@kernel.org>
2024-11-08 13:49 ` [PATCH backport to 6.10] x86/cpu: Add INTEL_FAM6_LUNARLAKE_M to X86_BUG_MONITOR Len Brown
2024-11-08 13:53 ` kernel test robot [this message]
2024-11-12 1:07 ` Thomas Gleixner
2024-11-08 13:49 ` [PATCH] x86/cpu: Add INTEL_LUNARLAKE_M " Len Brown
2024-11-08 14:34 ` Rafael J. Wysocki
2024-11-11 16:23 ` Peter Zijlstra
2024-11-12 0:27 ` Thomas Gleixner
[not found] ` <20241112053722.356303-1-lenb@kernel.org>
2024-11-12 5:28 ` [PATCH 1/1] " Len Brown
2024-11-12 11:44 ` Rafael J. Wysocki
[not found] ` <CAJvTdKnRpDQKUVNJ4Gp7r+WaHo0y-Wume3ay7toHU+Xz0gv2Zw@mail.gmail.com>
2024-11-12 13:14 ` Rafael J. Wysocki
[not found] ` <CAJvTdK=SnRqwjR5fUatP0CzaXD_CpZ-1cc+2yX0D8_XM_3oJUw@mail.gmail.com>
2024-11-12 15:02 ` Rafael J. Wysocki
2024-11-11 20:20 ` [PATCH] " Thomas Gleixner
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=Zy4X8lbLTKZlxOkH@0408e98e3aed \
--to=lkp@intel.com \
--cc=lenb@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox