public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Rui Qi <qirui.001@bytedance.com>
Cc: stable@vger.kernel.org, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH 3/3] x86/speculation: Support intra-function call validation
Date: Mon, 26 Feb 2024 18:12:59 +0800	[thread overview]
Message-ID: <ZdxkK5uArTDX6I5d@fdb2c0c3c270> (raw)
In-Reply-To: <20240226094925.95835-4-qirui.001@bytedance.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 3/3] x86/speculation: Support intra-function call validation
Link: https://lore.kernel.org/stable/20240226094925.95835-4-qirui.001%40bytedance.com

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




  reply	other threads:[~2024-02-26 10:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-26  9:49 [PATCH 0/3] Support intra-function call validation Rui Qi
2024-02-26  9:49 ` [PATCH 1/3] objtool: is_fentry_call() crashes if call has no destination Rui Qi
2024-02-26 13:29   ` Greg KH
2024-02-26  9:49 ` [PATCH 2/3] objtool: Add support for intra-function calls Rui Qi
2024-02-26  9:49 ` [PATCH 3/3] x86/speculation: Support intra-function call validation Rui Qi
2024-02-26 10:12   ` kernel test robot [this message]
2024-02-26 11:33 ` [PATCH 0/3] " qirui
2024-02-26 17:28   ` Josh Poimboeuf
2024-02-28  2:50     ` [External] " Rui Qi
  -- strict thread matches above, loose matches on Subject: below --
2024-02-26  9:40 $(name)
2024-02-26  9:41 ` [PATCH 3/3] x86/speculation: " $(name)
2024-02-26 10:06   ` kernel test robot

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=ZdxkK5uArTDX6I5d@fdb2c0c3c270 \
    --to=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=qirui.001@bytedance.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