From: kernel test robot <lkp@intel.com>
To: Ronak Doshi <doshir@vmware.com>
Cc: stable@vger.kernel.org, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH v2 net 2/2] vmxnet3: use correct intrConf reference when using extended queues
Date: Wed, 30 Nov 2022 16:22:31 +0800 [thread overview]
Message-ID: <Y4cSx2xpF6v4Non6@0d7994225921> (raw)
In-Reply-To: <20221130082148.9605-3-doshir@vmware.com>
Hi,
Thanks for your patch.
FYI: kernel test robot notices the stable kernel rule is not satisfied.
Rule: 'Cc: stable@vger.kernel.org' or 'commit <sha1> upstream.'
Subject: [PATCH v2 net 2/2] vmxnet3: use correct intrConf reference when using extended queues
Link: https://lore.kernel.org/stable/20221130082148.9605-3-doshir%40vmware.com
The check is based on https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
--
0-DAY CI Kernel Test Service
https://01.org/lkp
next prev parent reply other threads:[~2022-11-30 8:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 8:21 [PATCH v2 net 0/2] vmxnet3: couple of fixes Ronak Doshi
2022-11-30 8:21 ` [PATCH v2 net 1/2] vmxnet3: correctly report encapsulated LRO packet Ronak Doshi
2022-11-30 8:21 ` [PATCH v2 net 2/2] vmxnet3: use correct intrConf reference when using extended queues Ronak Doshi
2022-11-30 8:22 ` kernel test robot [this message]
2022-12-02 10:40 ` [PATCH v2 net 0/2] vmxnet3: couple of fixes patchwork-bot+netdevbpf
-- strict thread matches above, loose matches on Subject: below --
2022-12-05 22:42 Ronak Doshi
2022-12-05 22:42 ` [PATCH v2 net 2/2] vmxnet3: use correct intrConf reference when using extended queues Ronak Doshi
2022-12-05 22:43 ` 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=Y4cSx2xpF6v4Non6@0d7994225921 \
--to=lkp@intel.com \
--cc=doshir@vmware.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 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.