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/5] Clean up XDR encoders for NFSv4 READDIR
Date: Mon, 09 Oct 2023 13:36:59 -0400 [thread overview]
Message-ID: <9b15512bf345bea99218a7682fd9cc5d10cda9c5.camel@kernel.org> (raw)
In-Reply-To: <169642681764.7503.2925922561588558142.stgit@klimt.1015granger.net>
On Wed, 2023-10-04 at 09:41 -0400, Chuck Lever wrote:
> Tidy up the server-side XDR encoders for READDIR results and
> directory entries. 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 (5):
> NFSD: Rename nfsd4_encode_dirent()
> NFSD: Clean up nfsd4_encode_rdattr_error()
> NFSD: Add an nfsd4_encode_nfs_cookie4() helper
> NFSD: Clean up nfsd4_encode_entry4()
> NFSD: Clean up nfsd4_encode_readdir()
>
>
> fs/nfsd/nfs4xdr.c | 200 +++++++++++++++++++++++-----------------------
> fs/nfsd/xdr4.h | 3 +
> 2 files changed, 104 insertions(+), 99 deletions(-)
>
> --
> Chuck Lever
>
Reviewed-by: Jeff Layton <jlayton@kernel.org>
prev parent reply other threads:[~2023-10-09 17:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-04 13:41 [PATCH v1 0/5] Clean up XDR encoders for NFSv4 READDIR Chuck Lever
2023-10-04 13:41 ` [PATCH v1 1/5] NFSD: Rename nfsd4_encode_dirent() Chuck Lever
2023-10-04 13:41 ` [PATCH v1 2/5] NFSD: Clean up nfsd4_encode_rdattr_error() Chuck Lever
2023-10-04 13:41 ` [PATCH v1 3/5] NFSD: Add an nfsd4_encode_nfs_cookie4() helper Chuck Lever
2023-10-04 13:42 ` [PATCH v1 4/5] NFSD: Clean up nfsd4_encode_entry4() Chuck Lever
2023-10-04 13:42 ` [PATCH v1 5/5] NFSD: Clean up nfsd4_encode_readdir() Chuck Lever
2023-10-09 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=9b15512bf345bea99218a7682fd9cc5d10cda9c5.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 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.