linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: edward.shishkin@gmail.com
To: Eric Van Hensbergen <ericvh@gmail.com>,
	V9FS Developers Mailing List
	<v9fs-developer@lists.sourceforge.net>,
	Linux Filesystem Development List <linux-fsdevel@vger.kernel.org>
Cc: QEMU Developers Mailing List <qemu-devel@nongnu.org>,
	ZhangWei <zhangwei555@huawei.com>,
	Claudio Fontana <Claudio.Fontana@huawei.com>,
	Greg Kurz <groug@kaod.org>, Alexander Graf <agraf@suse.de>,
	kbuild test robot <fengguang.wu@intel.com>,
	Eduard Shishkin <eduard.shishkin@huawei.com>
Subject: [PATCH 5/7] 9p: v9fs fix semicolon.cocci warnings
Date: Mon, 12 Dec 2016 19:15:40 +0100	[thread overview]
Message-ID: <1481566542-25894-5-git-send-email-edward.shishkin@gmail.com> (raw)
In-Reply-To: <1481566542-25894-1-git-send-email-edward.shishkin@gmail.com>

From: kbuild test robot <fengguang.wu@intel.com>

fs/9p/vfs_addr.c:425:3-4: Unneeded semicolon
fs/9p/vfs_addr.c:458:2-3: Unneeded semicolon

 Remove unneeded semicolon.

Generated by: scripts/coccinelle/misc/semicolon.cocci

Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
Signed-off-by: Eduard Shishkin <eduard.shishkin@huawei.com>
---
 fs/9p/vfs_addr.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/fs/9p/vfs_addr.c b/fs/9p/vfs_addr.c
index 4ad248e..afd8a13 100644
--- a/fs/9p/vfs_addr.c
+++ b/fs/9p/vfs_addr.c
@@ -576,7 +576,7 @@ static int flush_pages(struct page **pages, int nr_pages,
 #endif
 				goto iter_send;
 			}
-		};
+		}
 	iter_send:
 		if (iter_len == 0)
 			/*
@@ -609,7 +609,7 @@ static int flush_pages(struct page **pages, int nr_pages,
 	next_iter:
 		if (ctx->done)
 			return ret;
-	};
+	}
 	return 0;
 }
 
-- 
2.7.4


  parent reply	other threads:[~2016-12-12 18:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-10 17:24 [RFC][PATCH 0/2] 9p: v9fs read and write speedup Edward Shishkin
2016-10-10 17:24 ` [PATCH 1/2] 9p: v9fs add writepages Edward Shishkin
2016-10-10 17:24   ` [PATCH 2/2] 9p: v9fs new readpages Edward Shishkin
2016-10-25 14:13     ` [Qemu-devel] " Alexander Graf
2016-12-09 18:42       ` Edward Shishkin
2016-10-25 14:01   ` [Qemu-devel] [PATCH 1/2] 9p: v9fs add writepages Alexander Graf
2016-12-09 18:43     ` Edward Shishkin
2016-12-12 18:13 ` [RFC][PATCH 0/7] 9p: v9fs read and write speedup - V2 Edward Shishkin
2016-12-12 18:15   ` [PATCH 1/7] 9p: v9fs add writepages edward.shishkin
2016-12-12 18:15     ` [PATCH 2/7] 9p: v9fs new readpages edward.shishkin
2016-12-12 18:15     ` [PATCH 3/7] 9p: v9fs fix ifnullfree.cocci warnings edward.shishkin
2016-12-12 18:15     ` [PATCH 4/7] 9p: v9fs fix odd_ptr_err.cocci warnings edward.shishkin
2016-12-12 18:15     ` edward.shishkin [this message]
2016-12-12 18:15     ` [PATCH 6/7] 9p: v9fs fix readpages writepages contexts allocation edward.shishkin
2016-12-12 18:15     ` [PATCH 7/7] 9p: v9fs fix calculation of max number of merged pages edward.shishkin

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=1481566542-25894-5-git-send-email-edward.shishkin@gmail.com \
    --to=edward.shishkin@gmail.com \
    --cc=Claudio.Fontana@huawei.com \
    --cc=agraf@suse.de \
    --cc=eduard.shishkin@huawei.com \
    --cc=ericvh@gmail.com \
    --cc=fengguang.wu@intel.com \
    --cc=groug@kaod.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    --cc=v9fs-developer@lists.sourceforge.net \
    --cc=zhangwei555@huawei.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).