From: kbuild test robot <fengguang.wu@intel.com>
Cc: Jaegeuk Kim <jaegeuk@kernel.org>,
kbuild-all@01.org, linux-f2fs-devel@lists.sourceforge.net
Subject: [PATCH] f2fs: fix semicolon.cocci warnings
Date: Thu, 2 Jun 2016 10:25:57 +0800 [thread overview]
Message-ID: <20160602022557.GA39165@lkp-sb04> (raw)
In-Reply-To: <201606021055.CQP21puy%fengguang.wu@intel.com>
fs/f2fs/checkpoint.c:887:2-3: Unneeded semicolon
Remove unneeded semicolon.
Generated by: scripts/coccinelle/misc/semicolon.cocci
Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
---
checkpoint.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/fs/f2fs/checkpoint.c
+++ b/fs/f2fs/checkpoint.c
@@ -884,7 +884,7 @@ int f2fs_sync_inode_meta(struct f2fs_sb_
update_inode_page(inode);
iput(inode);
}
- };
+ }
return 0;
}
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
next prev parent reply other threads:[~2016-06-02 2:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-02 2:25 [f2fs:dev-test 6/21] fs/f2fs/checkpoint.c:887:2-3: Unneeded semicolon kbuild test robot
2016-06-02 2:25 ` kbuild test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-10-31 10:21 [f2fs:dev-test 49/54] fs/f2fs/node.c:1811:2-3: " kbuild test robot
2017-10-31 10:21 ` [PATCH] f2fs: fix semicolon.cocci warnings kbuild test robot
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=20160602022557.GA39165@lkp-sb04 \
--to=fengguang.wu@intel.com \
--cc=jaegeuk@kernel.org \
--cc=kbuild-all@01.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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).