qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Alexander Graf <agraf@suse.de>, Anthony Liguori <anthony@codemonkey.ws>
Cc: "Cornelia Huck" <cornelia.huck@de.ibm.com>,
	"Christian Borntraeger" <borntraeger@de.ibm.com>,
	"Jens Freimann" <jfrei@linux.vnet.ibm.com>,
	"Andreas Färber" <afaerber@suse.de>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] [PULL 1/7] s390x/kvm: Fix switch/case indentation for handle_diag
Date: Fri, 30 Aug 2013 14:41:27 +0200	[thread overview]
Message-ID: <1377866493-47164-2-git-send-email-borntraeger@de.ibm.com> (raw)
In-Reply-To: <1377866493-47164-1-git-send-email-borntraeger@de.ibm.com>

This alignes case statements to switch statements in the handle_diag
function as mandated by coding style.

Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
---
 target-s390x/kvm.c | 20 ++++++++++----------
 1 file changed, 10 insertions(+), 10 deletions(-)

diff --git a/target-s390x/kvm.c b/target-s390x/kvm.c
index 26d18e3..ed80154 100644
--- a/target-s390x/kvm.c
+++ b/target-s390x/kvm.c
@@ -583,16 +583,16 @@ static int handle_diag(S390CPU *cpu, struct kvm_run *run, int ipb_code)
     int r = 0;
 
     switch (ipb_code) {
-        case DIAG_KVM_HYPERCALL:
-            r = handle_hypercall(cpu, run);
-            break;
-        case DIAG_KVM_BREAKPOINT:
-            sleep(10);
-            break;
-        default:
-            DPRINTF("KVM: unknown DIAG: 0x%x\n", ipb_code);
-            r = -1;
-            break;
+    case DIAG_KVM_HYPERCALL:
+        r = handle_hypercall(cpu, run);
+        break;
+    case DIAG_KVM_BREAKPOINT:
+        sleep(10);
+        break;
+    default:
+        DPRINTF("KVM: unknown DIAG: 0x%x\n", ipb_code);
+        r = -1;
+        break;
     }
 
     return r;
-- 
1.8.3.1

  reply	other threads:[~2013-08-30 13:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-30 12:41 [Qemu-devel] [PULLv2 0/7] s390x/kvm kdump and reset related changes Christian Borntraeger
2013-08-30 12:41 ` Christian Borntraeger [this message]
2013-08-30 12:41 ` [Qemu-devel] [PULLv2 2/7] s390/kvm: basic implementation of diagnose 308 subcode 6 Christian Borntraeger
2013-08-30 12:41 ` [Qemu-devel] [PULL 3/7] s390: provide I/O subsystem reset Christian Borntraeger
2013-08-30 12:41 ` [Qemu-devel] [PULL 4/7] s390: provide a cpu load normal function Christian Borntraeger
2013-08-30 12:41 ` [Qemu-devel] [PULLv2 5/7] s390/cpu: split CPU reset into architectured functions Christian Borntraeger
2013-08-30 12:41 ` [Qemu-devel] [PULLv2 6/7] s390: Implement load normal reset Christian Borntraeger
2013-08-30 12:41 ` [Qemu-devel] [PULL 7/7] s390: wire up nmi command to raise a RESTART interrupt on S390 Christian Borntraeger
2013-08-30 12:58 ` [Qemu-devel] [PULLv2 0/7] s390x/kvm kdump and reset related changes 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=1377866493-47164-2-git-send-email-borntraeger@de.ibm.com \
    --to=borntraeger@de.ibm.com \
    --cc=afaerber@suse.de \
    --cc=agraf@suse.de \
    --cc=anthony@codemonkey.ws \
    --cc=cornelia.huck@de.ibm.com \
    --cc=jfrei@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).