linux-kernel - Re: [PATCH] NFSD: Fix space and spelling mistake

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <098E693F-6F7A-4F55-84AE-21FE7498B940@oracle.com>
Date:   Thu, 23 Jun 2022 14:11:07 +0000
From:   Chuck Lever III <chuck.lever@...cle.com>
To:     Zhang Jiaming <jiaming@...china.com>
CC:     Jeff Layton <jlayton@...nel.org>,
        Linux NFS Mailing List <linux-nfs@...r.kernel.org>,
        LKML <linux-kernel@...r.kernel.org>,
        "liqiong@...chin.com" <liqiong@...chin.com>,
        "renyu@...china.com" <renyu@...china.com>
Subject: Re: [PATCH] NFSD: Fix space and spelling mistake



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