From: kernel test robot <lkp@intel.com>
To: Cindy Lu <lulu@redhat.com>
Cc: stable@vger.kernel.org, oe-kbuild-all@lists.linux.dev
Subject: Re: [RFC v2 1/4] vduse: Add function to get/free the pages for reconnection
Date: Tue, 12 Sep 2023 11:01:23 +0800 [thread overview]
Message-ID: <ZP/Ugy0vLvmomlWG@0091dd92274c> (raw)
In-Reply-To: <20230912030008.3599514-2-lulu@redhat.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: [RFC v2 1/4] vduse: Add function to get/free the pages for reconnection
Link: https://lore.kernel.org/stable/20230912030008.3599514-2-lulu%40redhat.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-09-12 3:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 3:00 [RFC v2 0/4] Support reconnection in vduse Cindy Lu
2023-09-12 3:00 ` [RFC v2 1/4] vduse: Add function to get/free the pages for reconnection Cindy Lu
2023-09-12 3:01 ` kernel test robot [this message]
2023-09-18 8:41 ` Jason Wang
2023-09-21 14:06 ` Cindy Lu
2023-09-12 3:00 ` [RFC v2 2/4] vduse: Add file operation for mmap Cindy Lu
2023-09-18 8:46 ` Jason Wang
2023-09-12 3:00 ` [RFC v2 3/4] vduse: update the vq_info in ioctl Cindy Lu
2023-09-12 7:39 ` Jason Wang
2023-09-25 4:15 ` Cindy Lu
2023-09-29 9:08 ` Maxime Coquelin
2023-09-29 9:12 ` Maxime Coquelin
2023-10-08 5:17 ` Jason Wang
2023-09-12 3:00 ` [RFC v2 4/4] vduse: Add new ioctl VDUSE_GET_RECONNECT_INFO Cindy Lu
2023-09-18 8:48 ` Jason Wang
2023-09-21 14:01 ` Cindy Lu
2023-09-25 2:57 ` Jason Wang
2023-09-25 3:19 ` Cindy Lu
2023-09-29 9:08 ` Maxime Coquelin
2023-10-09 3:00 ` Cindy Lu
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=ZP/Ugy0vLvmomlWG@0091dd92274c \
--to=lkp@intel.com \
--cc=lulu@redhat.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