From: kernel test robot <lkp@intel.com>
To: Nathan Chancellor <nathan@kernel.org>
Cc: stable@vger.kernel.org, oe-kbuild-all@lists.linux.dev
Subject: Re: Apply a1e2c031ec39 and e32683c6f7d2 to 5.15 and earlier
Date: Sat, 28 Oct 2023 01:47:55 +0800 [thread overview]
Message-ID: <ZTv3y8NB7A3KrFPF@dceb3e7df498> (raw)
In-Reply-To: <20231027160144.GA232578@dev-arch.thelio-3990X>
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: Apply a1e2c031ec39 and e32683c6f7d2 to 5.15 and earlier
Link: https://lore.kernel.org/stable/20231027160144.GA232578%40dev-arch.thelio-3990X
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next parent reply other threads:[~2023-10-27 17:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231027160144.GA232578@dev-arch.thelio-3990X>
2023-10-27 17:47 ` kernel test robot [this message]
2023-10-31 12:54 ` Apply a1e2c031ec39 and e32683c6f7d2 to 5.15 and earlier Greg Kroah-Hartman
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=ZTv3y8NB7A3KrFPF@dceb3e7df498 \
--to=lkp@intel.com \
--cc=nathan@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