From: zhouyang <zhouyang789@huawei.com>
To: <alex.bennee@linaro.org>
Cc: alex.chen@huawei.com, qemu-devel@nongnu.org, zhouyang789@huawei.com
Subject: [PATCH v3 2/5] contrib: Fix some code style problems, ERROR: "foo * bar" should be "foo *bar"
Date: Mon, 18 Jan 2021 11:10:01 +0800 [thread overview]
Message-ID: <20210118031004.1662363-3-zhouyang789@huawei.com> (raw)
In-Reply-To: <20210118031004.1662363-1-zhouyang789@huawei.com>
I am reading contrib related code and found some style problems while
check the code using checkpatch.pl. This commit fixs the issue below:
ERROR: "foo * bar" should be "foo *bar"
Signed-off-by: zhouyang <zhouyang789@huawei.com>
---
contrib/plugins/howvec.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/contrib/plugins/howvec.c b/contrib/plugins/howvec.c
index 6e602aaccf..2f892da17d 100644
--- a/contrib/plugins/howvec.c
+++ b/contrib/plugins/howvec.c
@@ -235,7 +235,7 @@ static void vcpu_insn_exec_before(unsigned int cpu_index, void *udata)
(*count)++;
}
-static uint64_t * find_counter(struct qemu_plugin_insn *insn)
+static uint64_t *find_counter(struct qemu_plugin_insn *insn)
{
int i;
uint64_t *cnt = NULL;
--
2.23.0
next prev parent reply other threads:[~2021-01-18 3:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 3:09 [PATCH v3 0/5] Fix some style problems in contrib zhouyang
2021-01-18 3:10 ` [PATCH v3 1/5] contrib: Don't use '#' flag of printf format zhouyang
2021-01-18 3:10 ` zhouyang [this message]
2021-01-18 3:10 ` [PATCH v3 3/5] contrib: Add spaces around operator zhouyang
2021-01-18 3:10 ` [PATCH v3 4/5] contrib: space required after that ',' zhouyang
2021-01-18 3:10 ` [PATCH v3 5/5] contrib: Open brace '{' following struct go on the same line zhouyang
2021-02-01 12:42 ` [PATCH v3 0/5] Fix some style problems in contrib zhouyang (T)
2021-02-02 14:40 ` Alex Bennée
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=20210118031004.1662363-3-zhouyang789@huawei.com \
--to=zhouyang789@huawei.com \
--cc=alex.bennee@linaro.org \
--cc=alex.chen@huawei.com \
--cc=qemu-devel@nongnu.org \
/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.