mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chuck Lever III <chuck.lever@oracle.com>
To: Zhang Jiaming <jiaming@nfschina.com>
Cc: Jeff Layton <jlayton@kernel.org>,
	Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	"liqiong@nfschin.com" <liqiong@nfschin.com>,
	"renyu@nfschina.com" <renyu@nfschina.com>
Subject: Re: [PATCH] NFSD: Fix space and spelling mistake
Date: Thu, 23 Jun 2022 14:11:07 +0000	[thread overview]
Message-ID: <098E693F-6F7A-4F55-84AE-21FE7498B940@oracle.com> (raw)
In-Reply-To: <20220623082005.8521-1-jiaming@nfschina.com>



> On Jun 23, 2022, at 4:20 AM, Zhang Jiaming <jiaming@nfschina.com> wrote:
> 
> Add a blank space after ','.
> Change 'succesful' to 'successful'.
> 
> Signed-off-by: Zhang Jiaming <jiaming@nfschina.com>

Thanks, applied for the next merge window.


> ---
> fs/nfsd/nfs4proc.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/fs/nfsd/nfs4proc.c b/fs/nfsd/nfs4proc.c
> index 3895eb52d2b1..d267b9bcf1fc 100644
> --- a/fs/nfsd/nfs4proc.c
> +++ b/fs/nfsd/nfs4proc.c
> @@ -828,7 +828,7 @@ nfsd4_create(struct svc_rqst *rqstp, struct nfsd4_compound_state *cstate,
> 			goto out_umask;
> 		status = nfsd_create(rqstp, &cstate->current_fh,
> 				     create->cr_name, create->cr_namelen,
> -				     &create->cr_iattr,S_IFCHR, rdev, &resfh);
> +				     &create->cr_iattr, S_IFCHR, rdev, &resfh);
> 		break;
> 
> 	case NF4SOCK:
> @@ -2711,7 +2711,7 @@ nfsd4_proc_compound(struct svc_rqst *rqstp)
> 		if (op->opdesc->op_flags & OP_MODIFIES_SOMETHING) {
> 			/*
> 			 * Don't execute this op if we couldn't encode a
> -			 * succesful reply:
> +			 * successful reply:
> 			 */
> 			u32 plen = op->opdesc->op_rsize_bop(rqstp, op);
> 			/*
> -- 
> 2.25.1
> 

--
Chuck Lever




      reply	other threads:[~2022-06-23 14:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-23  8:20 Zhang Jiaming
2022-06-23 14:11 ` Chuck Lever III [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=098E693F-6F7A-4F55-84AE-21FE7498B940@oracle.com \
    --to=chuck.lever@oracle.com \
    --cc=jiaming@nfschina.com \
    --cc=jlayton@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=liqiong@nfschin.com \
    --cc=renyu@nfschina.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

all inboxes | Powered by JetHome®