From: Bihong Yu <yubihong@huawei.com>
To: <qemu-devel@nongnu.org>, <qemu-trivial@nongnu.org>
Cc: yubihong@huawei.com, zhengchuan@huawei.com, quintela@redhat.com,
dgilbert@redhat.com, alex.chen@huawei.com, wanghao232@huawei.com
Subject: [PATCH v1 4/8] migration: Open brace '{' following struct go on the same line
Date: Sun, 11 Oct 2020 18:57:39 +0800 [thread overview]
Message-ID: <1602413863-19513-5-git-send-email-yubihong@huawei.com> (raw)
In-Reply-To: <1602413863-19513-1-git-send-email-yubihong@huawei.com>
Signed-off-by:Bihong Yu <yubihong@huawei.com>
Reviewed-by: Chuan Zheng <zhengchuan@huawei.com>
Signed-off-by: Bihong Yu <yubihong@huawei.com>
---
migration/migration.h | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/migration/migration.h b/migration/migration.h
index deb411a..99784b4 100644
--- a/migration/migration.h
+++ b/migration/migration.h
@@ -124,8 +124,7 @@ struct MigrationClass {
DeviceClass parent_class;
};
-struct MigrationState
-{
+struct MigrationState {
/*< private >*/
DeviceState parent_obj;
--
1.8.3.1
next prev parent reply other threads:[~2020-10-11 13:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-11 10:57 [PATCH v1 0/8] Fix some style problems in migration Bihong Yu
2020-10-11 10:57 ` [PATCH v1 1/8] migration: Do not use C99 // comments Bihong Yu
2020-10-11 10:57 ` [PATCH v1 2/8] migration: Don't use '#' flag of printf format Bihong Yu
2020-10-11 18:19 ` Peter Maydell
2020-10-12 12:45 ` Bihong Yu
2020-10-11 10:57 ` [PATCH v1 3/8] migration: Add spaces around operator Bihong Yu
2020-10-11 10:57 ` Bihong Yu [this message]
2020-10-11 10:57 ` [PATCH v1 5/8] migration: Add braces {} for if statement Bihong Yu
2020-10-11 10:57 ` [PATCH v1 6/8] migration: Do not initialise statics and globals to 0 or NULL Bihong Yu
2020-10-11 10:57 ` [PATCH v1 7/8] migration: Open brace '{' following function declarations go on the next line Bihong Yu
2020-10-11 10:57 ` [PATCH v1 8/8] migration: Delete redundant spaces Bihong Yu
2020-10-11 14:48 ` [PATCH v1 0/8] Fix some style problems in migration no-reply
-- strict thread matches above, loose matches on Subject: below --
2020-10-11 10:48 Bihong Yu
2020-10-11 10:48 ` [PATCH v1 4/8] migration: Open brace '{' following struct go on the same line Bihong Yu
2020-10-11 10:17 [PATCH v1 0/8] Fix some style problems in migration Bihong Yu
2020-10-11 10:17 ` [PATCH v1 4/8] migration: Open brace '{' following struct go on the same line Bihong Yu
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=1602413863-19513-5-git-send-email-yubihong@huawei.com \
--to=yubihong@huawei.com \
--cc=alex.chen@huawei.com \
--cc=dgilbert@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=quintela@redhat.com \
--cc=wanghao232@huawei.com \
--cc=zhengchuan@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).