From: Jeff Layton <jlayton@kernel.org>
To: Li Lingfeng <lilingfeng3@huawei.com>,
chuck.lever@oracle.com, neilb@suse.de, okorniev@redhat.com,
kolga@netapp.com, Dai.Ngo@oracle.com, tom@talpey.com,
trondmy@hammerspace.com, linux-nfs@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: yukuai1@huaweicloud.com, houtao1@huawei.com, yi.zhang@huawei.com,
yangerkun@huawei.com, lilingfeng@huaweicloud.com
Subject: Re: [PATCH 0/2] nfsd: add a new mapping and remove the redundant one
Date: Mon, 27 Jan 2025 09:52:42 -0500 [thread overview]
Message-ID: <2f2cc7c86601328a458dc32482681364b4a22fca.camel@kernel.org> (raw)
In-Reply-To: <20250126095045.738902-1-lilingfeng3@huawei.com>
On Sun, 2025-01-26 at 17:50 +0800, Li Lingfeng wrote:
> Add a new mapping and delete a redundant one.
>
> Li Lingfeng (2):
> nfsd: map the ELOOP to nfserr_symlink to avoid warning
> nfsd: remove the redundant mapping of nfserr_mlink
>
> fs/nfsd/vfs.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
Reviewed-by: Jeff Layton <jlayton@kernel.org>
prev parent reply other threads:[~2025-01-27 14:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-26 9:50 [PATCH 0/2] nfsd: add a new mapping and remove the redundant one Li Lingfeng
2025-01-26 9:50 ` [PATCH 1/2] nfsd: map the ELOOP to nfserr_symlink to avoid warning Li Lingfeng
2025-01-26 17:27 ` Chuck Lever
2025-01-27 2:33 ` Li Lingfeng
2025-01-27 13:28 ` Chuck Lever
2025-02-05 1:53 ` Li Lingfeng
2025-02-05 14:54 ` Chuck Lever
2025-02-06 1:09 ` NeilBrown
2025-01-26 9:50 ` [PATCH 2/2] nfsd: remove the redundant mapping of nfserr_mlink Li Lingfeng
2025-01-26 19:01 ` [PATCH 0/2] nfsd: add a new mapping and remove the redundant one cel
2025-01-27 14:52 ` 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=2f2cc7c86601328a458dc32482681364b4a22fca.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=Dai.Ngo@oracle.com \
--cc=chuck.lever@oracle.com \
--cc=houtao1@huawei.com \
--cc=kolga@netapp.com \
--cc=lilingfeng3@huawei.com \
--cc=lilingfeng@huaweicloud.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--cc=okorniev@redhat.com \
--cc=tom@talpey.com \
--cc=trondmy@hammerspace.com \
--cc=yangerkun@huawei.com \
--cc=yi.zhang@huawei.com \
--cc=yukuai1@huaweicloud.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