From: Max Reitz <mreitz@redhat.com>
To: qemu-block@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
qemu-devel@nongnu.org, Max Reitz <mreitz@redhat.com>
Subject: [Qemu-devel] [PULL 00/11] Block patches for rc1
Date: Mon, 15 Jul 2019 16:28:54 +0200 [thread overview]
Message-ID: <20190715142905.9078-1-mreitz@redhat.com> (raw)
The following changes since commit b9404bf592e7ba74180e1a54ed7a266ec6ee67f2:
Merge remote-tracking branch 'remotes/dgilbert/tags/pull-hmp-20190715' into staging (2019-07-15 12:22:07 +0100)
are available in the Git repository at:
https://github.com/XanClic/qemu.git tags/pull-block-2019-07-15
for you to fetch changes up to 0b1847bbc2b4f50e7497cb05c4540bf7b016c9c6:
gluster: fix .bdrv_reopen_prepare when backing file is a JSON object (2019-07-15 15:48:41 +0200)
----------------------------------------------------------------
Block patches for 4.1-rc1:
- Fixes for the NVMe block driver, the gluster block driver, and for
running multiple block jobs concurrently on a single chain
----------------------------------------------------------------
Max Reitz (9):
block: Add BDS.never_freeze
block/stream: Fix error path
block/stream: Swap backing file change order
block: Deep-clear inherits_from
iotests: Fix throttling in 030
iotests: Compare error messages in 030
iotests: Add @use_log to VM.run_job()
iotests: Add new case to 030
iotests: Add read-only test case to 030
Michal Privoznik (1):
nvme: Set number of queues later in nvme_init()
Stefano Garzarella (1):
gluster: fix .bdrv_reopen_prepare when backing file is a JSON object
include/block/block_int.h | 3 +
block.c | 42 +++++++---
block/commit.c | 4 +
block/gluster.c | 12 ++-
block/mirror.c | 4 +
block/nvme.c | 2 +-
block/stream.c | 4 +-
tests/qemu-iotests/030 | 150 +++++++++++++++++++++++++++-------
tests/qemu-iotests/030.out | 4 +-
tests/qemu-iotests/iotests.py | 18 ++--
10 files changed, 193 insertions(+), 50 deletions(-)
--
2.21.0
next reply other threads:[~2019-07-15 14:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-15 14:28 Max Reitz [this message]
2019-07-15 14:28 ` [Qemu-devel] [PULL 01/11] nvme: Set number of queues later in nvme_init() Max Reitz
2019-07-15 14:28 ` [Qemu-devel] [PULL 02/11] block: Add BDS.never_freeze Max Reitz
2019-07-15 14:28 ` [Qemu-devel] [PULL 03/11] block/stream: Fix error path Max Reitz
2019-07-15 14:28 ` [Qemu-devel] [PULL 04/11] block/stream: Swap backing file change order Max Reitz
2019-07-15 14:28 ` [Qemu-devel] [PULL 05/11] block: Deep-clear inherits_from Max Reitz
2019-07-15 14:29 ` [Qemu-devel] [PULL 06/11] iotests: Fix throttling in 030 Max Reitz
2019-07-15 14:29 ` [Qemu-devel] [PULL 07/11] iotests: Compare error messages " Max Reitz
2019-07-15 14:29 ` [Qemu-devel] [PULL 08/11] iotests: Add @use_log to VM.run_job() Max Reitz
2019-07-15 14:29 ` [Qemu-devel] [PULL 09/11] iotests: Add new case to 030 Max Reitz
2019-07-15 14:29 ` [Qemu-devel] [PULL 10/11] iotests: Add read-only test " Max Reitz
2019-07-15 14:29 ` [Qemu-devel] [PULL 11/11] gluster: fix .bdrv_reopen_prepare when backing file is a JSON object Max Reitz
2019-07-15 15:56 ` [Qemu-devel] [PULL 00/11] Block patches for rc1 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=20190715142905.9078-1-mreitz@redhat.com \
--to=mreitz@redhat.com \
--cc=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).