From: Kevin Wolf <kwolf@redhat.com>
To: qemu-block@nongnu.org
Cc: kwolf@redhat.com, peter.maydell@linaro.org, qemu-devel@nongnu.org
Subject: [Qemu-devel] [PULL 0/3] Block layer patches
Date: Tue, 27 Nov 2018 15:06:37 +0100 [thread overview]
Message-ID: <20181127140640.24830-1-kwolf@redhat.com> (raw)
The following changes since commit d5d31c9a8ab5e87db4230602a6fd5da8eb13135c:
Merge remote-tracking branch 'remotes/ehabkost/tags/x86-for-3.1-pull-request' into staging (2018-11-27 09:55:05 +0000)
are available in the Git repository at:
git://repo.or.cz/qemu/kevin.git tags/for-upstream
for you to fetch changes up to 6da021815e752b3ca3a547eed53f3e92a8a35452:
nvme: Fix spurious interrupts (2018-11-27 12:59:00 +0100)
----------------------------------------------------------------
Block layer patches:
- block: Fix crash on migration with explicit child nodes
- nvme: Fix spurious interrupts
----------------------------------------------------------------
Keith Busch (1):
nvme: Fix spurious interrupts
Kevin Wolf (2):
block: Don't inactivate children before parents
iotests: Test migration with -blockdev
block.c | 84 +++++++++++++++++++------------
hw/block/nvme.c | 4 +-
tests/qemu-iotests/234 | 121 +++++++++++++++++++++++++++++++++++++++++++++
tests/qemu-iotests/234.out | 30 +++++++++++
tests/qemu-iotests/group | 1 +
5 files changed, 208 insertions(+), 32 deletions(-)
create mode 100755 tests/qemu-iotests/234
create mode 100644 tests/qemu-iotests/234.out
next reply other threads:[~2018-11-27 14:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-27 14:06 Kevin Wolf [this message]
2018-11-27 14:06 ` [Qemu-devel] [PULL 1/3] block: Don't inactivate children before parents Kevin Wolf
2018-11-27 14:06 ` [Qemu-devel] [PULL 2/3] iotests: Test migration with -blockdev Kevin Wolf
2018-11-27 14:06 ` [Qemu-devel] [PULL 3/3] nvme: Fix spurious interrupts Kevin Wolf
2018-11-27 15:34 ` [Qemu-devel] [PULL 0/3] Block layer 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=20181127140640.24830-1-kwolf@redhat.com \
--to=kwolf@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-block@nongnu.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).