From: Christian Schoenebeck <qemu_oss@crudebyte.com>
To: qemu-devel@nongnu.org, Peter Maydell <peter.maydell@linaro.org>
Cc: Greg Kurz <groug@kaod.org>,
Xinhao Zhang <zhangxinhao1@huawei.com>,
Kai Deng <dengkai1@huawei.com>
Subject: [PULL 3/4] hw/9pfs : add space before the open parenthesis '('
Date: Fri, 06 Nov 2020 10:13:10 +0100 [thread overview]
Message-ID: <22e13675874dabcb314de98134fe6142cd9864a7.1604653990.git.qemu_oss@crudebyte.com> (raw)
In-Reply-To: <cover.1604653990.git.qemu_oss@crudebyte.com>
From: Xinhao Zhang <zhangxinhao1@huawei.com>
Fix code style. Space required before the open parenthesis '('.
Signed-off-by: Xinhao Zhang <zhangxinhao1@huawei.com>
Signed-off-by: Kai Deng <dengkai1@huawei.com>
Reported-by: Euler Robot <euler.robot@huawei.com>
Reviewed-by: Greg Kurz <groug@kaod.org>
Message-Id: <20201030043515.1030223-3-zhangxinhao1@huawei.com>
Signed-off-by: Christian Schoenebeck <qemu_oss@crudebyte.com>
---
hw/9pfs/cofs.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/hw/9pfs/cofs.c b/hw/9pfs/cofs.c
index 55991916ec..0b321b456e 100644
--- a/hw/9pfs/cofs.c
+++ b/hw/9pfs/cofs.c
@@ -23,7 +23,7 @@ static ssize_t __readlink(V9fsState *s, V9fsPath *path, V9fsString *buf)
ssize_t len, maxlen = PATH_MAX;
buf->data = g_malloc(PATH_MAX);
- for(;;) {
+ for (;;) {
len = s->ops->readlink(&s->ctx, path, buf->data, maxlen);
if (len < 0) {
g_free(buf->data);
--
2.20.1
next prev parent reply other threads:[~2020-11-06 9:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-06 9:13 [PULL 0/4] 9p queue for 5.2 (2020-11-06) Christian Schoenebeck
2020-11-06 9:13 ` Christian Schoenebeck [this message]
2020-11-06 9:13 ` [PULL 4/4] hw/9pfs: Fix Kconfig dependency problem between 9pfs and Xen Christian Schoenebeck
2020-11-06 9:13 ` [PULL 1/4] hw/9pfs : add spaces around operator Christian Schoenebeck
2020-11-06 9:13 ` [PULL 2/4] hw/9pfs : open brace '{' following struct go on the same line Christian Schoenebeck
2020-11-06 10:34 ` [PULL 0/4] 9p queue for 5.2 (2020-11-06) Peter Maydell
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=22e13675874dabcb314de98134fe6142cd9864a7.1604653990.git.qemu_oss@crudebyte.com \
--to=qemu_oss@crudebyte.com \
--cc=dengkai1@huawei.com \
--cc=groug@kaod.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=zhangxinhao1@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).