All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Chuck Lever <cel@kernel.org>
Cc: stable@vger.kernel.org, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH 1/2] NFSD: Fix "start of NFS reply" pointer passed to nfsd_cache_update()
Date: Wed, 29 Nov 2023 05:59:55 +0800	[thread overview]
Message-ID: <ZWZi2y1vDXZF9BBJ@520bc4c78bef> (raw)
In-Reply-To: <170120871426.1376.10151990384789497254.stgit@klimt.1015granger.net>

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 1/2] NFSD: Fix "start of NFS reply" pointer passed to nfsd_cache_update()
Link: https://lore.kernel.org/stable/170120871426.1376.10151990384789497254.stgit%40klimt.1015granger.net

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki




  reply	other threads:[~2023-11-28 22:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-28 21:58 [PATCH 0/2] nfsd fixes for 6.6.y Chuck Lever
2023-11-28 21:58 ` [PATCH 1/2] NFSD: Fix "start of NFS reply" pointer passed to nfsd_cache_update() Chuck Lever
2023-11-28 21:59   ` kernel test robot [this message]
2023-11-28 21:58 ` [PATCH 2/2] NFSD: Fix checksum mismatches in the duplicate reply cache Chuck Lever
2023-11-28 22:05 ` [PATCH 0/2] nfsd fixes for 6.6.y Chuck Lever III
2023-11-30 13:28   ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2023-11-28 22:01 [PATCH 0/2] nfsd fixes for 6.1.y Chuck Lever
2023-11-28 22:01 ` [PATCH 1/2] NFSD: Fix "start of NFS reply" pointer passed to nfsd_cache_update() Chuck Lever

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=ZWZi2y1vDXZF9BBJ@520bc4c78bef \
    --to=lkp@intel.com \
    --cc=cel@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 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.