From: Qian Lu <luqia@amazon.com>
To: <gregkh@linuxfoundation.org>
Cc: <stable@vger.kernel.org>, <trond.myklebust@hammerspace.com>,
zhangliguang <zhangliguang@linux.alibaba.com>,
Qian Lu <luqia@amazon.com>
Subject: [PATCH 4/4] NFS: Remove redundant semicolon
Date: Wed, 31 Jul 2019 00:13:27 -0700 [thread overview]
Message-ID: <20190731071327.28701-5-luqia@amazon.com> (raw)
In-Reply-To: <20190731071327.28701-1-luqia@amazon.com>
From: zhangliguang <zhangliguang@linux.alibaba.com>
commit 42f72cf368c502c435af4e206e26d651cfb7d9ad upstream.
This removes redundant semicolon for ending code.
Fixes: c7944ebb9ce9 ("NFSv4: Fix lookup revalidate of regular files")
Signed-off-by: Liguang Zhang <zhangliguang@linux.alibaba.com>
Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
Cc: <stable@vger.kernel.org> # 4.14.x
Signed-off-by: Qian Lu <luqia@amazon.com>
---
fs/nfs/dir.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/nfs/dir.c b/fs/nfs/dir.c
index 85a6fdd76e20..9065db7c31eb 100644
--- a/fs/nfs/dir.c
+++ b/fs/nfs/dir.c
@@ -1635,7 +1635,7 @@ nfs4_do_lookup_revalidate(struct inode *dir, struct dentry *dentry,
reval_dentry:
if (flags & LOOKUP_RCU)
return -ECHILD;
- return nfs_lookup_revalidate_dentry(dir, dentry, inode);;
+ return nfs_lookup_revalidate_dentry(dir, dentry, inode);
full_reval:
return nfs_do_lookup_revalidate(dir, dentry, flags);
--
2.15.3.AMZN
next prev parent reply other threads:[~2019-07-31 7:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-31 7:13 [PATCH 0/4] Fix NFSv4 lookup revalidation Qian Lu
2019-07-31 7:13 ` [PATCH 1/4] NFS: Fix dentry revalidation on NFSv4 lookup Qian Lu
2019-07-31 7:13 ` [PATCH 2/4] NFS: Refactor nfs_lookup_revalidate() Qian Lu
2019-07-31 7:13 ` [PATCH 3/4] NFSv4: Fix lookup revalidate of regular files Qian Lu
2019-07-31 7:13 ` Qian Lu [this message]
2019-07-31 9:33 ` [PATCH 4/4] NFS: Remove redundant semicolon Greg KH
2019-07-31 9:34 ` [PATCH 0/4] Fix NFSv4 lookup revalidation Greg KH
2019-07-31 16:12 ` Qian Lu
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=20190731071327.28701-5-luqia@amazon.com \
--to=luqia@amazon.com \
--cc=gregkh@linuxfoundation.org \
--cc=stable@vger.kernel.org \
--cc=trond.myklebust@hammerspace.com \
--cc=zhangliguang@linux.alibaba.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;
as well as URLs for NNTP newsgroup(s).