qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Xinhao Zhang <zhangxinhao1@huawei.com>
To: <qemu-devel@nongnu.org>
Cc: alex.chen@huawei.com, peter.maydell@linaro.org,
	qemu-arm@nongnu.org, qemu-trivial@nongnu.org,
	dengkai1@huawei.com
Subject: [PATCH 3/3] target/arm: add space before the open parenthesis '('
Date: Tue, 3 Nov 2020 19:45:29 +0800	[thread overview]
Message-ID: <20201103114529.638233-3-zhangxinhao1@huawei.com> (raw)
In-Reply-To: <20201103114529.638233-1-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>
---
 target/arm/translate.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/target/arm/translate.c b/target/arm/translate.c
index 38371db540..efa3b59d04 100644
--- a/target/arm/translate.c
+++ b/target/arm/translate.c
@@ -9094,7 +9094,7 @@ static void arm_tr_tb_stop(DisasContextBase *dcbase, CPUState *cpu)
             - Hardware watchpoints.
            Hardware breakpoints have already been handled and skip this code.
          */
-        switch(dc->base.is_jmp) {
+        switch (dc->base.is_jmp) {
         case DISAS_NEXT:
         case DISAS_TOO_MANY:
             gen_goto_tb(dc, 1, dc->base.pc_next);
-- 
2.29.0-rc1



  parent reply	other threads:[~2020-11-03 11:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-03 11:45 [PATCH 1/3] target/arm: add spaces around operator Xinhao Zhang
2020-11-03 11:45 ` [PATCH 2/3] target/arm: Don't use '#' flag of printf format Xinhao Zhang
2020-11-03 11:45 ` Xinhao Zhang [this message]
2020-11-04 18:04 ` [PATCH 1/3] target/arm: add spaces around operator Peter Maydell
2020-11-05 10:20   ` 答复: " zhangxinhao

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=20201103114529.638233-3-zhangxinhao1@huawei.com \
    --to=zhangxinhao1@huawei.com \
    --cc=alex.chen@huawei.com \
    --cc=dengkai1@huawei.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@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 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).