From: Cornelia Huck <cohuck@redhat.com>
To: qemu-devel@nongnu.org
Cc: borntraeger@de.ibm.com, agraf@suse.de, david@redhat.com,
zyimin@linux.vnet.ibm.com, pasic@linux.vnet.ibm.com,
jjherne@linux.vnet.ibm.com, dgilbert@redhat.com,
Cornelia Huck <cohuck@redhat.com>
Subject: [Qemu-devel] [PATCH 0/1] s390x: more zpci compat fun
Date: Tue, 26 Sep 2017 18:20:57 +0200 [thread overview]
Message-ID: <20170926162058.30772-1-cohuck@redhat.com> (raw)
Here's a (hopefully) less hackish variant of the fix in
<932ad4e2-a10c-77fc-fcb7-5dbbed0d2c7c@de.ibm.com>. Not really tested
(I had problems reproducing the problem on z12, but that might be
just me).
Please review & test, if possible. Patch against my s390-next branch
(but should fix on top of master as well, I think.)
Cornelia Huck (1):
s390x: create a compat s390 phb for <=2.10
hw/s390x/s390-virtio-ccw.c | 8 +++++++-
include/hw/s390x/s390-virtio-ccw.h | 1 +
2 files changed, 8 insertions(+), 1 deletion(-)
--
2.13.5
next reply other threads:[~2017-09-26 16:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-26 16:20 Cornelia Huck [this message]
2017-09-26 16:20 ` [Qemu-devel] [PATCH 1/1] s390x: create a compat s390 phb for <=2.10 Cornelia Huck
2017-09-26 17:07 ` Christian Borntraeger
2017-09-26 18:40 ` David Hildenbrand
2017-09-27 9:47 ` Cornelia Huck
2017-09-27 10:25 ` Yi Min Zhao
2017-09-27 10:56 ` Cornelia Huck
2017-09-27 10:59 ` Christian Borntraeger
2017-09-27 12:21 ` David Hildenbrand
2017-09-27 12:26 ` Christian Borntraeger
2017-09-27 14:28 ` Dr. David Alan Gilbert
2017-09-27 14:46 ` Cornelia Huck
2017-09-27 14:49 ` Dr. David Alan Gilbert
2017-09-27 15:03 ` Cornelia Huck
2017-09-28 10:34 ` Christian Borntraeger
2017-09-28 10:41 ` Christian Borntraeger
2017-09-28 12:07 ` Cornelia Huck
2017-09-28 12:17 ` Christian Borntraeger
2017-09-28 12:27 ` Cornelia Huck
2017-09-28 12:33 ` David Hildenbrand
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=20170926162058.30772-1-cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--cc=dgilbert@redhat.com \
--cc=jjherne@linux.vnet.ibm.com \
--cc=pasic@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=zyimin@linux.vnet.ibm.com \
/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).