From: kernel test robot <lkp@intel.com>
To: Jedrzej Jagielski <jedrzej.jagielski@intel.com>
Cc: stable@vger.kernel.org, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH iwl-net v1 2/4] ixgbe: handle IXGBE_VF_GET_PF_LINK_STATE mailbox operation
Date: Thu, 28 Aug 2025 18:12:06 +0800 [thread overview]
Message-ID: <aLArdkpnBnD3yyOR@5fc77bca29d8> (raw)
In-Reply-To: <20250828095227.1857066-3-jedrzej.jagielski@intel.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 iwl-net v1 2/4] ixgbe: handle IXGBE_VF_GET_PF_LINK_STATE mailbox operation
Link: https://lore.kernel.org/stable/20250828095227.1857066-3-jedrzej.jagielski%40intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-08-28 10:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-28 9:52 [PATCH iwl-net v1 0/4] ixgbe/ixgbevf: fix PF/VF communication issues Jedrzej Jagielski
2025-08-28 9:52 ` [PATCH iwl-net v1 1/4] ixgbevf: fix getting link speed data for E610 devices Jedrzej Jagielski
2025-09-19 8:15 ` [Intel-wired-lan] " Romanowski, Rafal
2025-08-28 9:52 ` [PATCH iwl-net v1 2/4] ixgbe: handle IXGBE_VF_GET_PF_LINK_STATE mailbox operation Jedrzej Jagielski
2025-08-28 10:12 ` kernel test robot [this message]
2025-09-19 8:15 ` [Intel-wired-lan] " Romanowski, Rafal
2025-08-28 9:52 ` [PATCH iwl-net v1 3/4] ixgbevf: fix mailbox API compatibility by negotiating supported features Jedrzej Jagielski
2025-09-19 8:16 ` [Intel-wired-lan] " Romanowski, Rafal
2025-08-28 9:52 ` [PATCH iwl-net v1 4/4] ixgbe: handle IXGBE_VF_FEATURES_NEGOTIATE mbox cmd Jedrzej Jagielski
2025-09-19 8:16 ` [Intel-wired-lan] " Romanowski, Rafal
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=aLArdkpnBnD3yyOR@5fc77bca29d8 \
--to=lkp@intel.com \
--cc=jedrzej.jagielski@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