From: jokenzhang <zhangxinhao1@huawei.com>
To: <qemu-devel@nongnu.org>
Cc: alex.chen@huawei.com, qemu-trivial@nongnu.org,
qemu_oss@crudebyte.com, groug@kaod.org, dengkai1@huawei.com
Subject: [PATCH v2 2/3] hw/9pfs : open brace '{' following struct go on the same line
Date: Thu, 29 Oct 2020 22:26:18 +0800 [thread overview]
Message-ID: <20201029142619.1309649-2-zhangxinhao1@huawei.com> (raw)
In-Reply-To: <20201029142619.1309649-1-zhangxinhao1@huawei.com>
Fix code style. Open braces for struct should go on the same line.
Signed-off-by: jokenzhang <zhangxinhao1@huawei.com>
Signed-off-by: Kai Deng <dengkai1@huawei.com>
Reported-by: Euler Robot <euler.robot@huawei.com>
---
hw/9pfs/9p.h | 9 +++------
1 file changed, 3 insertions(+), 6 deletions(-)
diff --git a/hw/9pfs/9p.h b/hw/9pfs/9p.h
index 3dd1b50b1a..32df81f360 100644
--- a/hw/9pfs/9p.h
+++ b/hw/9pfs/9p.h
@@ -143,8 +143,7 @@ typedef struct {
*/
QEMU_BUILD_BUG_ON(sizeof(P9MsgHeader) != 7);
-struct V9fsPDU
-{
+struct V9fsPDU {
uint32_t size;
uint16_t tag;
uint8_t id;
@@ -270,8 +269,7 @@ union V9fsFidOpenState {
void *private;
};
-struct V9fsFidState
-{
+struct V9fsFidState {
int fid_type;
int32_t fid;
V9fsPath path;
@@ -338,8 +336,7 @@ typedef struct {
uint64_t path;
} QpfEntry;
-struct V9fsState
-{
+struct V9fsState {
QLIST_HEAD(, V9fsPDU) free_list;
QLIST_HEAD(, V9fsPDU) active_list;
V9fsFidState *fid_list;
--
2.29.0-rc1
next prev parent reply other threads:[~2020-10-29 14:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-29 14:26 [PATCH v2 1/3] hw/9pfs : add spaces around operator jokenzhang
2020-10-29 14:26 ` jokenzhang [this message]
2020-10-29 14:26 ` [PATCH v2 3/3] hw/9pfs : add space before the open parenthesis '(' jokenzhang
2020-10-29 15:04 ` [PATCH v2 1/3] hw/9pfs : add spaces around operator Greg Kurz
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=20201029142619.1309649-2-zhangxinhao1@huawei.com \
--to=zhangxinhao1@huawei.com \
--cc=alex.chen@huawei.com \
--cc=dengkai1@huawei.com \
--cc=groug@kaod.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=qemu_oss@crudebyte.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 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.