From: Cornelia Huck <cornelia.huck@de.ibm.com>
To: peter.maydell@linaro.org
Cc: borntraeger@de.ibm.com, agraf@suse.de, jfrei@linux.vnet.ibm.com,
qemu-devel@nongnu.org, Cornelia Huck <cornelia.huck@de.ibm.com>
Subject: [Qemu-devel] [PULL 0/3] s390x fixes for 2.7
Date: Wed, 20 Jul 2016 16:17:22 +0200 [thread overview]
Message-ID: <20160720141725.20025-1-cornelia.huck@de.ibm.com> (raw)
ck/qemu s390x-20160720
The following changes since commit 1ecfb24da987b862fd46a5b37292879952ea9e7d:
Merge remote-tracking branch 'remotes/riku/tags/pull-linux-user-20160719-2' into staging (2016-07-20 11:32:12 +0100)
are available in the git repository at:
git://github.com/cohuck/qemu tags/s390x-20160720
for you to fetch changes up to 2a79eb1a616a07b0e8c41430f03af254fefe219d:
s390x/css: provide a dev_path for css devices (2016-07-20 15:47:25 +0200)
----------------------------------------------------------------
Fixes for s390x in the css area.
----------------------------------------------------------------
Cornelia Huck (1):
s390x/css: provide a dev_path for css devices
Sascha Silbe (2):
s390x/css: copy CCW format bit from ORB to SCSW
s390x/css: sch_handle_start_func() handles resume, too
hw/s390x/css-bridge.c | 26 +++++++++++++++++++++++++-
hw/s390x/css.c | 5 +++++
hw/s390x/s390-virtio-ccw.c | 4 ++++
include/hw/s390x/css-bridge.h | 7 +++++++
4 files changed, 41 insertions(+), 1 deletion(-)
--
2.9.2
next reply other threads:[~2016-07-20 14:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-20 14:17 Cornelia Huck [this message]
2016-07-20 14:17 ` [Qemu-devel] [PULL 1/3] s390x/css: copy CCW format bit from ORB to SCSW Cornelia Huck
2016-07-20 14:17 ` [Qemu-devel] [PULL 2/3] s390x/css: sch_handle_start_func() handles resume, too Cornelia Huck
2016-07-20 14:17 ` [Qemu-devel] [PULL 3/3] s390x/css: provide a dev_path for css devices Cornelia Huck
2016-07-20 20:32 ` [Qemu-devel] [PULL 0/3] s390x fixes for 2.7 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=20160720141725.20025-1-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).