From: Chuck Lever <chuck.lever@oracle.com>
To: Li Lingfeng <lilingfeng3@huawei.com>
Cc: "trondmy@kernel.org" <trondmy@kernel.org>,
"anna@kernel.org" <anna@kernel.org>,
"jlayton@kernel.org" <jlayton@kernel.org>,
"neilb@suse.de" <neilb@suse.de>,
"kolga@netapp.com" <kolga@netapp.com>,
Dai Ngo <dai.ngo@oracle.com>, "tom@talpey.com" <tom@talpey.com>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"yukuai1@huaweicloud.com" <yukuai1@huaweicloud.com>,
"houtao1@huawei.com" <houtao1@huawei.com>,
"yi.zhang@huawei.com" <yi.zhang@huawei.com>,
"yangerkun@huawei.com" <yangerkun@huawei.com>,
"lilingfeng@huaweicloud.com" <lilingfeng@huaweicloud.com>
Subject: Re: [PATCH v2 2/2] nfsd: fix some spelling errors in comments
Date: Sat, 24 Aug 2024 11:54:02 -0400 [thread overview]
Message-ID: <ZsoCGmEs9LjQf0JZ@tissot.1015granger.net> (raw)
In-Reply-To: <20240824014336.537937-3-lilingfeng3@huawei.com>
On Fri, Aug 23, 2024 at 09:43:36PM -0400, Li Lingfeng wrote:
> Fix spelling errors in comments of nfsd4_release_lockowner and
> nfs4_set_delegation.
>
> Signed-off-by: Li Lingfeng <lilingfeng3@huawei.com>
> ---
> fs/nfsd/nfs4state.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> [...]
Applied to nfsd-next for v6.12, thanks!
[2/2] nfsd: fix some spelling errors in comments
commit: 2a6dfb4ce8136b93e38e1101636af44ed82b3d3e
--
Chuck Lever
prev parent reply other threads:[~2024-08-24 15:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-24 1:43 [PATCH v2 0/2] nfs/nfsd: fix some comments Li Lingfeng
2024-08-24 1:43 ` [PATCH v2 1/2] nfs: fix the comment of nfs_get_root Li Lingfeng
2024-08-24 1:43 ` [PATCH v2 2/2] nfsd: fix some spelling errors in comments Li Lingfeng
2024-08-24 15:54 ` Chuck Lever [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=ZsoCGmEs9LjQf0JZ@tissot.1015granger.net \
--to=chuck.lever@oracle.com \
--cc=anna@kernel.org \
--cc=dai.ngo@oracle.com \
--cc=houtao1@huawei.com \
--cc=jlayton@kernel.org \
--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=tom@talpey.com \
--cc=trondmy@kernel.org \
--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