From: Jeff Layton <jlayton@kernel.org>
To: NeilBrown <neilb@suse.de>, Chuck Lever <chuck.lever@oracle.com>
Cc: linux-nfs@vger.kernel.org, Olga Kornievskaia <kolga@netapp.com>,
Dai Ngo <Dai.Ngo@oracle.com>, Tom Talpey <tom@talpey.com>
Subject: Re: [PATCH 0/3] nfsd: move error code mapping to per-version code
Date: Mon, 29 Jul 2024 08:36:32 -0400 [thread overview]
Message-ID: <bf355b20806eec6df7abcc19212c139db49b4260.camel@kernel.org> (raw)
In-Reply-To: <20240729014940.23053-1-neilb@suse.de>
On Mon, 2024-07-29 at 11:47 +1000, NeilBrown wrote:
> These three patches replace my earlier patch
> [PATCH 3/6] nfsd: Move error code mapping to per-version xdr
> code.
>
> The mapping is now in proc code, not xdr code.
>
> NeilBrown
>
> [PATCH 1/3] nfsd: Move error code mapping to per-version proc code.
> [PATCH 2/3] nfsd: be more systematic about selecting error codes for
> [PATCH 3/3] nfsd: move error choice for incorrect object types to
Nice cleanup! Much cleaner than having all of this error handling
sprinkled all over the generic code.
Reviewed-by: Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2024-07-29 12:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-29 1:47 [PATCH 0/3] nfsd: move error code mapping to per-version code NeilBrown
2024-07-29 1:47 ` [PATCH 1/3] nfsd: Move error code mapping to per-version proc code NeilBrown
2024-07-29 15:04 ` Christoph Hellwig
2024-07-29 1:47 ` [PATCH 2/3] nfsd: be more systematic about selecting error codes for internal use NeilBrown
2024-07-29 15:05 ` Christoph Hellwig
2024-07-29 1:47 ` [PATCH 3/3] nfsd: move error choice for incorrect object types to version-specific code NeilBrown
2024-07-29 15:06 ` Christoph Hellwig
2024-08-08 10:37 ` Jeff Layton
2024-08-08 11:40 ` NeilBrown
2024-08-08 12:01 ` Jeff Layton
2024-08-08 22:00 ` NeilBrown
2024-08-09 12:34 ` Jeff Layton
2024-07-29 12:36 ` Jeff Layton [this message]
2024-07-29 15:16 ` [PATCH 0/3] nfsd: move error code mapping to per-version code Chuck Lever
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=bf355b20806eec6df7abcc19212c139db49b4260.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=Dai.Ngo@oracle.com \
--cc=chuck.lever@oracle.com \
--cc=kolga@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--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