From: Kevin Wolf <kwolf@redhat.com>
To: qemu-block@nongnu.org
Cc: kwolf@redhat.com, peter.maydell@linaro.org, qemu-devel@nongnu.org
Subject: [PULL 0/3] Block layer patches for 5.1.0-rc1
Date: Tue, 21 Jul 2020 17:46:34 +0200 [thread overview]
Message-ID: <20200721154637.220022-1-kwolf@redhat.com> (raw)
The following changes since commit 90218a9a393c7925f330e7dcc08658e2a01d3bd4:
Merge remote-tracking branch 'remotes/huth-gitlab/tags/pull-request-2020-07-21' into staging (2020-07-21 10:24:38 +0100)
are available in the Git repository at:
git://repo.or.cz/qemu/kevin.git tags/for-upstream
for you to fetch changes up to 4a01e27ddcb5921efd68820d05d85ba71293fea6:
iotests: Test sparseness for qemu-img convert -n (2020-07-21 17:44:35 +0200)
----------------------------------------------------------------
Block layer patches:
- file-posix: Handle `EINVAL` fallocate return value
- qemu-img convert -n: Keep qcow2 v2 target sparse
----------------------------------------------------------------
Antoine Damhet (1):
file-posix: Handle `EINVAL` fallocate return value
Kevin Wolf (2):
qcow2: Implement v2 zero writes with discard if possible
iotests: Test sparseness for qemu-img convert -n
block/file-posix.c | 6 +++++-
block/qcow2-cluster.c | 9 ++++++++-
tests/qemu-iotests/122 | 30 ++++++++++++++++++++++++++++++
tests/qemu-iotests/122.out | 17 +++++++++++++++++
4 files changed, 60 insertions(+), 2 deletions(-)
next reply other threads:[~2020-07-21 15:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-21 15:46 Kevin Wolf [this message]
2020-07-21 15:46 ` [PULL 1/3] file-posix: Handle `EINVAL` fallocate return value Kevin Wolf
2020-07-21 15:46 ` [PULL 2/3] qcow2: Implement v2 zero writes with discard if possible Kevin Wolf
2020-07-21 15:46 ` [PULL 3/3] iotests: Test sparseness for qemu-img convert -n Kevin Wolf
2020-07-21 19:28 ` [PULL 0/3] Block layer patches for 5.1.0-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=20200721154637.220022-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).