qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jens Freimann <jfrei@linux.vnet.ibm.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>,
	Alexander Graf <agraf@suse.de>,
	Cornelia Huck <cornelia.huck@de.ibm.com>
Cc: David Hildenbrand <dahi@linux.vnet.ibm.com>,
	Jens Freimann <jfrei@linux.vnet.ibm.com>,
	qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH 4/5] s390x/gdb: coding style fixes
Date: Fri, 29 Aug 2014 15:52:17 +0200	[thread overview]
Message-ID: <1409320338-63098-5-git-send-email-jfrei@linux.vnet.ibm.com> (raw)
In-Reply-To: <1409320338-63098-1-git-send-email-jfrei@linux.vnet.ibm.com>

From: David Hildenbrand <dahi@linux.vnet.ibm.com>

This patch cleanes up two coding style issues (missing whitespaces).

Signed-off-by: David Hildenbrand <dahi@linux.vnet.ibm.com>
Acked-by: Cornelia Huck <cornelia.huck@de.ibm.com>
Acked-by: Christian Borntraeger <borntraeger@de.ibm.com>
Signed-off-by: Jens Freimann <jfrei@linux.vnet.ibm.com>
---
 target-s390x/gdbstub.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/target-s390x/gdbstub.c b/target-s390x/gdbstub.c
index cda8053..8945f02 100644
--- a/target-s390x/gdbstub.c
+++ b/target-s390x/gdbstub.c
@@ -41,7 +41,7 @@ int s390_cpu_gdb_read_register(CPUState *cs, uint8_t *mem_buf, int n)
     case S390_PSWA_REGNUM:
         return gdb_get_regl(mem_buf, env->psw.addr);
     case S390_R0_REGNUM ... S390_R15_REGNUM:
-        return gdb_get_regl(mem_buf, env->regs[n-S390_R0_REGNUM]);
+        return gdb_get_regl(mem_buf, env->regs[n - S390_R0_REGNUM]);
     }
     return 0;
 }
@@ -63,7 +63,7 @@ int s390_cpu_gdb_write_register(CPUState *cs, uint8_t *mem_buf, int n)
         env->psw.addr = tmpl;
         break;
     case S390_R0_REGNUM ... S390_R15_REGNUM:
-        env->regs[n-S390_R0_REGNUM] = tmpl;
+        env->regs[n - S390_R0_REGNUM] = tmpl;
         break;
     default:
         return 0;
-- 
1.8.5.5

  parent reply	other threads:[~2014-08-29 13:53 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-29 13:52 [Qemu-devel] [PATCH 0/5] s390x/gdb: various fixes Jens Freimann
2014-08-29 13:52 ` [Qemu-devel] [PATCH 1/5] s390x/gdb: don't touch the cc if tcg is not enabled Jens Freimann
2014-09-01 22:39   ` Alexander Graf
2014-09-02  7:07     ` Christian Borntraeger
2014-09-03  9:27       ` Alexander Graf
2014-09-05  7:29         ` Christian Borntraeger
2014-08-29 13:52 ` [Qemu-devel] [PATCH 2/5] s390x/gdb: add the feature xml files for s390x Jens Freimann
2014-08-29 13:52 ` [Qemu-devel] [PATCH 3/5] s390x/gdb: generate target.xml and handle fp/ac as coprocessors Jens Freimann
2014-08-29 13:52 ` Jens Freimann [this message]
2014-08-29 13:52 ` [Qemu-devel] [PATCH 5/5] gdb: provide the name of the architecture in the target.xml Jens Freimann
2014-09-01 10:19   ` Peter Maydell
2014-09-01 10:25     ` Andreas Färber
2014-09-01 10:31     ` Christian Borntraeger
2014-09-01 10:32       ` Peter Maydell
2014-09-03  9:37     ` David Hildenbrand
2014-09-03  9:45       ` Edgar E. Iglesias
2014-09-03  9:59         ` David Hildenbrand
2014-09-03 10:00           ` Edgar E. Iglesias
2014-09-01 10:06 ` [Qemu-devel] [PATCH 0/5] s390x/gdb: various fixes Christian Borntraeger
2014-09-01 22:43   ` Alexander Graf

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=1409320338-63098-5-git-send-email-jfrei@linux.vnet.ibm.com \
    --to=jfrei@linux.vnet.ibm.com \
    --cc=agraf@suse.de \
    --cc=borntraeger@de.ibm.com \
    --cc=cornelia.huck@de.ibm.com \
    --cc=dahi@linux.vnet.ibm.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 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).