Linux NFS development
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: Chuck Lever <cel@kernel.org>, linux-nfs@vger.kernel.org
Cc: Chuck Lever <chuck.lever@oracle.com>
Subject: Re: [PATCH v1 0/8] Clean up miscellaneous NFSv4 XDR encoders
Date: Tue, 10 Oct 2023 11:22:16 -0400	[thread overview]
Message-ID: <105a77ad8fa0ebaf9a3ccc8d29e8f9e60b5ea96e.camel@kernel.org> (raw)
In-Reply-To: <169687606447.41382.568611605570999245.stgit@oracle-102.nfsv4bat.org>

On Mon, 2023-10-09 at 14:29 -0400, Chuck Lever wrote:
> Tidy up the server-side XDR result encoders for remaining
> miscellanous NFSv4 operations. Series applies to nfsd-next. See
> topic branch "nfsd4-encoder-overhaul" in this repo:
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/cel/linux.git
> 
> ---
> 
> Chuck Lever (8):
>       NFSD: Clean up nfsd4_encode_access()
>       NFSD: Clean up nfsd4_do_encode_secinfo()
>       NFSD: Clean up nfsd4_encode_exchange_id()
>       NFSD: Clean up nfsd4_encode_test_stateid()
>       NFSD: Clean up nfsd4_encode_copy()
>       NFSD: Clean up nfsd4_encode_copy_notify()
>       NFSD: Clean up nfsd4_encode_offset_status()
>       NFSD: Clean up nfsd4_encode_seek()
> 
> 
>  fs/nfsd/nfs4proc.c |   4 +-
>  fs/nfsd/nfs4xdr.c  | 419 ++++++++++++++++++++++++---------------------
>  fs/nfsd/xdr4.h     |   4 +-
>  3 files changed, 225 insertions(+), 202 deletions(-)
> 
> --
> Chuck Lever
> 

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

      parent reply	other threads:[~2023-10-10 15:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-09 18:29 [PATCH v1 0/8] Clean up miscellaneous NFSv4 XDR encoders Chuck Lever
2023-10-09 18:29 ` [PATCH v1 1/8] NFSD: Clean up nfsd4_encode_access() Chuck Lever
2023-10-09 18:29 ` [PATCH v1 2/8] NFSD: Clean up nfsd4_do_encode_secinfo() Chuck Lever
2023-10-09 18:29 ` [PATCH v1 3/8] NFSD: Clean up nfsd4_encode_exchange_id() Chuck Lever
2023-10-09 18:30 ` [PATCH v1 4/8] NFSD: Clean up nfsd4_encode_test_stateid() Chuck Lever
2023-10-09 18:30 ` [PATCH v1 5/8] NFSD: Clean up nfsd4_encode_copy() Chuck Lever
2023-10-09 18:30 ` [PATCH v1 6/8] NFSD: Clean up nfsd4_encode_copy_notify() Chuck Lever
2023-10-09 18:30 ` [PATCH v1 7/8] NFSD: Clean up nfsd4_encode_offset_status() Chuck Lever
2023-10-09 18:30 ` [PATCH v1 8/8] NFSD: Clean up nfsd4_encode_seek() Chuck Lever
2023-10-10 15:22 ` 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=105a77ad8fa0ebaf9a3ccc8d29e8f9e60b5ea96e.camel@kernel.org \
    --to=jlayton@kernel.org \
    --cc=cel@kernel.org \
    --cc=chuck.lever@oracle.com \
    --cc=linux-nfs@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