From: "KaiLong Wang" <wangkailong@jari.cn>
To: chuck.lever@oracle.com, jlayton@kernel.org, neilb@suse.de,
kolga@netapp.com, Dai.Ngo@oracle.com, tom@talpey.com
Cc: linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] NFSD: Clean up errors in nfs4xdr.c
Date: Fri, 13 Oct 2023 14:39:51 +0800 (GMT+08:00) [thread overview]
Message-ID: <116353ed.95a.18b27c347d9.Coremail.wangkailong@jari.cn> (raw)
Fix the following errors reported by checkpatch:
ERROR: spaces required around that '=' (ctx:VxV)
ERROR: else should follow close brace '}'
Signed-off-by: KaiLong Wang <wangkailong@jari.cn>
---
fs/nfsd/nfs4xdr.c | 7 +++----
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/fs/nfsd/nfs4xdr.c b/fs/nfsd/nfs4xdr.c
index 1cbd2a392302..8b9707957649 100644
--- a/fs/nfsd/nfs4xdr.c
+++ b/fs/nfsd/nfs4xdr.c
@@ -2432,7 +2432,7 @@ nfsd4_decode_compound(struct nfsd4_compoundargs *argp)
{
struct nfsd4_op *op;
bool cachethis = false;
- int auth_slack= argp->rqstp->rq_auth_slack;
+ int auth_slack = argp->rqstp->rq_auth_slack;
int max_reply = auth_slack + 8; /* opcnt, status */
int readcount = 0;
int readbytes = 0;
@@ -2585,7 +2585,7 @@ static __be32 nfsd4_encode_components_esc(struct xdr_stream *xdr, char sep,
__be32 *p;
__be32 pathlen;
int pathlen_offset;
- int strlen, count=0;
+ int strlen, count = 0;
char *str, *end, *next;
dprintk("nfsd4_encode_components(%s)\n", components);
@@ -2622,8 +2622,7 @@ static __be32 nfsd4_encode_components_esc(struct xdr_stream *xdr, char sep,
return nfserr_resource;
p = xdr_encode_opaque(p, str, strlen);
count++;
- }
- else
+ } else
end++;
if (found_esc)
end = next;
--
2.17.1
next reply other threads:[~2023-10-13 6:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-13 6:39 KaiLong Wang [this message]
2023-10-13 10:50 ` [PATCH] NFSD: Clean up errors in nfs4xdr.c Jeff Layton
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=116353ed.95a.18b27c347d9.Coremail.wangkailong@jari.cn \
--to=wangkailong@jari.cn \
--cc=Dai.Ngo@oracle.com \
--cc=chuck.lever@oracle.com \
--cc=jlayton@kernel.org \
--cc=kolga@netapp.com \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.