qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Cornelia Huck <cornelia.huck@de.ibm.com>
To: peter.maydell@linaro.org
Cc: Cornelia Huck <cornelia.huck@de.ibm.com>,
	borntraeger@de.ibm.com, jfrei@linux.vnet.ibm.com,
	qemu-devel@nongnu.org, agraf@suse.de
Subject: [Qemu-devel] [PULL v2 2/9] s390x/virtio-ccw: fix 2.4 virtio compat
Date: Wed, 21 Oct 2015 12:30:02 +0200	[thread overview]
Message-ID: <1445423409-22218-3-git-send-email-cornelia.huck@de.ibm.com> (raw)
In-Reply-To: <1445423409-22218-1-git-send-email-cornelia.huck@de.ibm.com>

Commit 542571d5 ("virtio-ccw: enable virtio-1") missed some virtio
devices for the 2.4 compat handling. Add them.

Fixes: 542571d5 ("virtio-ccw: enable virtio-1")
Signed-off-by: Cornelia Huck <cornelia.huck@de.ibm.com>
Reviewed-by: Christian Borntraeger <borntraeger@de.ibm.com>
---
 hw/s390x/s390-virtio-ccw.c | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/hw/s390x/s390-virtio-ccw.c b/hw/s390x/s390-virtio-ccw.c
index 6195f13..b9033d4 100644
--- a/hw/s390x/s390-virtio-ccw.c
+++ b/hw/s390x/s390-virtio-ccw.c
@@ -262,6 +262,18 @@ static const TypeInfo ccw_machine_info = {
             .driver   = "virtio-rng-ccw",\
             .property = "max_revision",\
             .value    = "0",\
+        },{\
+            .driver   = "virtio-net-ccw",\
+            .property = "max_revision",\
+            .value    = "0",\
+        },{\
+            .driver   = "virtio-scsi-ccw",\
+            .property = "max_revision",\
+            .value    = "0",\
+        },{\
+            .driver   = "vhost-scsi-ccw",\
+            .property = "max_revision",\
+            .value    = "0",\
         },
 
 static void ccw_machine_2_4_class_init(ObjectClass *oc, void *data)
-- 
2.6.2

  parent reply	other threads:[~2015-10-21 10:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-21 10:30 [Qemu-devel] [PULL v2 0/9] Next set of s390x patches Cornelia Huck
2015-10-21 10:30 ` [Qemu-devel] [PULL v2 1/9] util/qemu-config: fix missing machine command line options Cornelia Huck
2015-10-21 10:30 ` Cornelia Huck [this message]
2015-10-21 10:30 ` [Qemu-devel] [PULL v2 3/9] s390x/kvm: Fix vector validity bit in device machine checks Cornelia Huck
2015-10-21 10:30 ` [Qemu-devel] [PULL v2 4/9] s390x: flagify mcic values Cornelia Huck
2015-10-21 10:30 ` [Qemu-devel] [PULL v2 5/9] s390x: unify device reset during subsystem_reset() Cornelia Huck
2015-10-21 10:30 ` [Qemu-devel] [PULL v2 6/9] s390x/ipl: we always have an ipl device Cornelia Huck
2015-10-21 10:30 ` [Qemu-devel] [PULL v2 7/9] s390x: machine reset function with new ipl cpu handling Cornelia Huck
2015-10-21 10:30 ` [Qemu-devel] [PULL v2 8/9] s390x: reset crypto only on clear reset and QEMU reset Cornelia Huck
2015-10-21 10:30 ` [Qemu-devel] [PULL v2 9/9] s390x/cmma: clean up cmma reset Cornelia Huck
2015-10-21 15:59 ` [Qemu-devel] [PULL v2 0/9] Next set of s390x patches Peter Maydell

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=1445423409-22218-3-git-send-email-cornelia.huck@de.ibm.com \
    --to=cornelia.huck@de.ibm.com \
    --cc=agraf@suse.de \
    --cc=borntraeger@de.ibm.com \
    --cc=jfrei@linux.vnet.ibm.com \
    --cc=peter.maydell@linaro.org \
    --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).