From: kernel test robot <lkp@intel.com>
To: Breno Leitao <leitao@debian.org>
Cc: stable@vger.kernel.org, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH net v3 2/3] selftest: netcons: refactor target creation
Date: Sat, 6 Sep 2025 01:27:25 +0800 [thread overview]
Message-ID: <aLsdfeTte3sIXnbr@b7823f61de85> (raw)
In-Reply-To: <20250905-netconsole_torture-v3-2-875c7febd316@debian.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-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 net v3 2/3] selftest: netcons: refactor target creation
Link: https://lore.kernel.org/stable/20250905-netconsole_torture-v3-2-875c7febd316%40debian.org
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-09-05 17:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-05 17:25 [PATCH net v3 0/3] net: netpoll: fix a memleak and create a selftest Breno Leitao
2025-09-05 17:25 ` [PATCH net v3 1/3] netpoll: fix incorrect refcount handling causing incorrect cleanup Breno Leitao
2025-09-08 10:12 ` Simon Horman
2025-09-08 20:47 ` Calvin Owens
2025-09-09 1:29 ` Jakub Kicinski
2025-09-09 20:17 ` Breno Leitao
2025-09-09 23:16 ` Jakub Kicinski
2025-09-10 14:12 ` Breno Leitao
2025-09-10 17:58 ` Jakub Kicinski
2025-09-10 18:50 ` Breno Leitao
2025-09-10 0:18 ` Jay Vosburgh
2025-09-10 14:07 ` Breno Leitao
2025-09-09 14:05 ` Breno Leitao
2025-09-10 0:40 ` Calvin Owens
2025-09-05 17:25 ` [PATCH net v3 2/3] selftest: netcons: refactor target creation Breno Leitao
2025-09-05 17:27 ` kernel test robot [this message]
2025-09-08 10:13 ` Simon Horman
2025-09-05 17:25 ` [PATCH net v3 3/3] selftest: netcons: create a torture test Breno Leitao
2025-09-08 10:13 ` Simon Horman
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=aLsdfeTte3sIXnbr@b7823f61de85 \
--to=lkp@intel.com \
--cc=leitao@debian.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.