Linux NFS development
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: Chuck Lever <cel@kernel.org>, NeilBrown <neil@brown.name>,
	Olga Kornievskaia <okorniev@redhat.com>,
	Dai Ngo <dai.ngo@oracle.com>, Tom Talpey <tom@talpey.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH v1 0/3] Clean up fs/nfsd/vfs.c includes
Date: Wed, 12 Aug 2026 13:36:50 -0400	[thread overview]
Message-ID: <b3a1318aff094018b6ca858f2ee9d4ee6d4340eb.camel@kernel.org> (raw)
In-Reply-To: <20260812142436.35042-1-cel@kernel.org>

On Wed, 2026-08-12 at 10:24 -0400, Chuck Lever wrote:
> A quick set of clean-ups that permit us to remove more version-
> specific material from fs/nfsd/vfs.c.
> 
> [ re-posting v1; the first post did not include linux-nfs@ ]
> 
> Chuck Lever (3):
>   NFSD: Make the write verifier reset helper available outside vfs.c
>   NFSD: Move NFSv4-specific CLONE logic into nfsd4_clone()
>   NFSD: Remove xdr-related headers from fs/nfsd/vfs.c
> 
>  fs/nfsd/nfs4proc.c |  27 ++++++++--
>  fs/nfsd/vfs.c      | 129 ++++++++++++++++++++++++++-------------------
>  fs/nfsd/vfs.h      |  14 +++--
>  3 files changed, 108 insertions(+), 62 deletions(-)

Reviewed-by: Jeff Layton <jlayton@kernel.org>

      parent reply	other threads:[~2026-08-12 17:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-12 14:24 [PATCH v1 0/3] Clean up fs/nfsd/vfs.c includes Chuck Lever
2026-08-12 14:24 ` [PATCH v1 1/3] NFSD: Make the write verifier reset helper available outside vfs.c Chuck Lever
2026-08-12 14:24 ` [PATCH v1 2/3] NFSD: Move NFSv4-specific CLONE logic into nfsd4_clone() Chuck Lever
2026-08-12 14:24 ` [PATCH v1 3/3] NFSD: Remove xdr-related headers from fs/nfsd/vfs.c Chuck Lever
2026-08-12 17:36 ` Jeff Layton [this message]

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=b3a1318aff094018b6ca858f2ee9d4ee6d4340eb.camel@kernel.org \
    --to=jlayton@kernel.org \
    --cc=cel@kernel.org \
    --cc=dai.ngo@oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=neil@brown.name \
    --cc=okorniev@redhat.com \
    --cc=tom@talpey.com \
    /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