Linux kernel -stable discussions
 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/8] NFSD: Refactor nfsd_reply_cache_free_locked()
Date: Wed, 29 Nov 2023 06:01:01 +0800	[thread overview]
Message-ID: <ZWZjHVscdrNKXRLv@520bc4c78bef> (raw)
In-Reply-To: <170120877882.1515.3190174495040446432.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/8] NFSD: Refactor nfsd_reply_cache_free_locked()
Link: https://lore.kernel.org/stable/170120877882.1515.3190174495040446432.stgit%40klimt.1015granger.net

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




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

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-28 21:59 [PATCH 0/8] nfsd fixes for 6.5.y Chuck Lever
2023-11-28 21:59 ` [PATCH 1/8] NFSD: Refactor nfsd_reply_cache_free_locked() Chuck Lever
2023-11-28 22:01   ` kernel test robot [this message]
2023-11-28 21:59 ` [PATCH 2/8] NFSD: Rename nfsd_reply_cache_alloc() Chuck Lever
2023-11-28 21:59 ` [PATCH 3/8] NFSD: Replace nfsd_prune_bucket() Chuck Lever
2023-11-28 21:59 ` [PATCH 4/8] NFSD: Refactor the duplicate reply cache shrinker Chuck Lever
2023-11-28 22:00 ` [PATCH 5/8] NFSD: Remove svc_rqst::rq_cacherep Chuck Lever
2023-11-28 22:00 ` [PATCH 6/8] NFSD: Rename struct svc_cacherep Chuck Lever
2023-11-28 22:00 ` [PATCH 7/8] NFSD: Fix "start of NFS reply" pointer passed to nfsd_cache_update() Chuck Lever
2023-11-28 22:00 ` [PATCH 8/8] NFSD: Fix checksum mismatches in the duplicate reply cache Chuck Lever
2023-11-28 22:07 ` [PATCH 0/8] nfsd fixes for 6.5.y Chuck Lever III
2023-11-30 13:25   ` Greg KH
2023-11-30 13:49     ` Chuck Lever III

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=ZWZjHVscdrNKXRLv@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox