From: Greg KH <gregkh@linuxfoundation.org>
To: kernel test robot <lkp@intel.com>
Cc: Jiri Olsa <jolsa@kernel.org>,
stable@vger.kernel.org, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCHv2 stable 6.1 1/2] btf, scripts: Exclude Rust CUs with pahole
Date: Wed, 17 Jan 2024 17:07:55 +0100 [thread overview]
Message-ID: <2024011746-aloha-ripcord-8dd7@gregkh> (raw)
In-Reply-To: <ZafYCmLzkWeqI6sF@fc6e15c3a4e0>
On Wed, Jan 17, 2024 at 09:37:14PM +0800, 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-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: [PATCHv2 stable 6.1 1/2] btf, scripts: Exclude Rust CUs with pahole
> Link: https://lore.kernel.org/stable/20240117133520.733288-2-jolsa%40kernel.org
False positive :(
next prev parent reply other threads:[~2024-01-17 16:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-17 13:35 [PATCHv2 stable 6.1 0/2] btf, scripts: Update pahole options Jiri Olsa
2024-01-17 13:35 ` [PATCHv2 stable 6.1 1/2] btf, scripts: Exclude Rust CUs with pahole Jiri Olsa
2024-01-17 13:37 ` kernel test robot
2024-01-17 16:07 ` Greg KH [this message]
2024-01-18 14:45 ` Yujie Liu
2024-01-17 13:35 ` [PATCHv2 stable 6.1 2/2] bpf: Add --skip_encoding_btf_inconsistent_proto, --btf_gen_optimized to pahole flags for v1.25 Jiri Olsa
2024-01-18 9:58 ` [PATCHv2 stable 6.1 0/2] btf, scripts: Update pahole options Greg KH
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=2024011746-aloha-ripcord-8dd7@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=jolsa@kernel.org \
--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