From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [PATCH] xfs: fix semicolon.cocci warnings
Date: Mon, 13 Apr 2020 20:46:40 +0800 [thread overview]
Message-ID: <20200413124639.GA77252@b7572e1f2996> (raw)
In-Reply-To: <202004132033.kArCvaGW%lkp@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1008 bytes --]
From: kbuild test robot <lkp@intel.com>
fs/xfs/libxfs/xfs_swapext.c:240:16-17: Unneeded semicolon
Remove unneeded semicolon.
Generated by: scripts/coccinelle/misc/semicolon.cocci
Fixes: 50f595c1bc68 ("xfs: create deferred log items for extent swapping")
Signed-off-by: kbuild test robot <lkp@intel.com>
---
tree: https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux.git djwong-wtf
head: 451e129b1d48285f45c3abcced1f7fe3516aa645
commit: 50f595c1bc68cc1db4f800833af9cc04838774ab [325/340] xfs: create deferred log items for extent swapping
xfs_swapext.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/fs/xfs/libxfs/xfs_swapext.c
+++ b/fs/xfs/libxfs/xfs_swapext.c
@@ -237,7 +237,7 @@ xfs_swapext_finish_one(
irec1.br_blockcount, &irec2, &nimaps,
bmap_flags);
if (error)
- return error;;
+ return error;
if (nimaps != 1 ||
irec2.br_startblock == DELAYSTARTBLOCK ||
irec2.br_startoff != sxi->si_startoff2) {
next prev parent reply other threads:[~2020-04-13 12:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-13 12:46 [djwong-xfs:djwong-wtf 325/340] fs/xfs/libxfs/xfs_swapext.c:240:16-17: Unneeded semicolon kbuild test robot
2020-04-13 12:46 ` kbuild test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-06-30 6:38 [PATCH 2/9] xfs: XLOG_STATE_IOERROR must die Dave Chinner
2021-06-30 15:22 ` [PATCH] xfs: fix semicolon.cocci warnings kernel test robot
2021-06-30 15:22 ` kernel test robot
[not found] <201706262342.mc5rV25t%fengguang.wu@intel.com>
2017-06-26 15:57 ` kbuild test robot
2017-06-26 15:52 ` Brian Foster
2017-06-26 15:54 ` Darrick J. Wong
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=20200413124639.GA77252@b7572e1f2996 \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
/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.