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 XDR encoders for pNFS operations
Date: Fri, 29 Sep 2023 12:34:11 -0400 [thread overview]
Message-ID: <01ac6657423d6f3a28aca457c5651c8bda12cd68.camel@kernel.org> (raw)
In-Reply-To: <169564827064.6013.5014460767978657478.stgit@klimt.1015granger.net>
On Mon, 2023-09-25 at 09:27 -0400, Chuck Lever wrote:
> Tidy up the server-side XDR encoders for pNFS-related operations.
> Note that this does not touch the layout driver code; that can be
> done later.
>
> 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: Add nfsd4_encode_count4()
> NFSD: Clean up nfsd4_encode_stateid()
> NFSD: Make @lgp parameter of ->encode_layoutget a const pointer
> NFSD: Clean up nfsd4_encode_layoutget()
> NFSD: Clean up nfsd4_encode_layoutcommit()
> NFSD: Clean up nfsd4_encode_layoutreturn()
> NFSD: Make @gdev parameter of ->encode_getdeviceinfo a const pointer
> NFSD: Clean up nfsd4_encode_getdeviceinfo()
>
>
> fs/nfsd/blocklayoutxdr.c | 6 +-
> fs/nfsd/blocklayoutxdr.h | 4 +-
> fs/nfsd/flexfilelayoutxdr.c | 6 +-
> fs/nfsd/flexfilelayoutxdr.h | 4 +-
> fs/nfsd/nfs4layouts.c | 6 +-
> fs/nfsd/nfs4proc.c | 4 +-
> fs/nfsd/nfs4xdr.c | 206 ++++++++++++++++++++----------------
> fs/nfsd/pnfs.h | 6 +-
> fs/nfsd/xdr4.h | 7 +-
> 9 files changed, 135 insertions(+), 114 deletions(-)
>
> --
> Chuck Lever
>
Looks good. Nice cleanup.
Reviewed-by: Jeff Layton <jlayton@kernel.org>
prev parent reply other threads:[~2023-09-29 16:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-25 13:27 [PATCH v1 0/8] Clean up XDR encoders for pNFS operations Chuck Lever
2023-09-25 13:27 ` [PATCH v1 1/8] NFSD: Add nfsd4_encode_count4() Chuck Lever
2023-09-25 13:27 ` [PATCH v1 2/8] NFSD: Clean up nfsd4_encode_stateid() Chuck Lever
2023-09-25 13:27 ` [PATCH v1 3/8] NFSD: Make @lgp parameter of ->encode_layoutget a const pointer Chuck Lever
2023-09-25 13:27 ` [PATCH v1 4/8] NFSD: Clean up nfsd4_encode_layoutget() Chuck Lever
2023-09-25 13:28 ` [PATCH v1 5/8] NFSD: Clean up nfsd4_encode_layoutcommit() Chuck Lever
2023-09-25 13:28 ` [PATCH v1 6/8] NFSD: Clean up nfsd4_encode_layoutreturn() Chuck Lever
2023-09-25 13:28 ` [PATCH v1 7/8] NFSD: Make @gdev parameter of ->encode_getdeviceinfo a const pointer Chuck Lever
2023-09-25 13:28 ` [PATCH v1 8/8] NFSD: Clean up nfsd4_encode_getdeviceinfo() Chuck Lever
2023-09-29 16:34 ` 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=01ac6657423d6f3a28aca457c5651c8bda12cd68.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;
as well as URLs for NNTP newsgroup(s).