From: Hanna Reitz <hreitz@redhat.com>
To: qemu-block@nongnu.org
Cc: Thomas Huth <thuth@redhat.com>, Kevin Wolf <kwolf@redhat.com>,
Hanna Reitz <hreitz@redhat.com>,
Vladimir Sementsov-Ogievskiy <v.sementsov-og@mail.ru>,
qemu-devel@nongnu.org
Subject: [PATCH v3 0/3] iotests: Check for zstd support
Date: Wed, 23 Mar 2022 11:55:19 +0100 [thread overview]
Message-ID: <20220323105522.53660-1-hreitz@redhat.com> (raw)
Hi,
v1 cover letter:
https://lists.nongnu.org/archive/html/qemu-devel/2022-02/msg04592.html
v2 cover letter:
https://lists.nongnu.org/archive/html/qemu-block/2022-03/msg00041.html
Thanks a lot for the review and testing on v2; but I missed that I’d
have to send v3 because qemu_img_pipe_and_status() has just been
removed, which was used in patch 1 of v2. :/
v3:
- Patch 1: Use qemu_img(check=False) instead of
qemu_img_pipe_and_status()
- Patch 2: Rebase-caused import conflict
git backport-diff against v2:
Key:
[----] : patches are identical
[####] : number of functional differences between upstream/downstream patch
[down] : patch is downstream-only
The flags [FC] indicate (F)unctional and (C)ontextual differences, respectively
001/3:[0011] [FC] 'iotests.py: Add supports_qcow2_zstd_compression()'
002/3:[0004] [FC] 'iotests/065: Check for zstd support'
003/3:[----] [--] 'iotests/303: Check for zstd support'
Hanna Reitz (3):
iotests.py: Add supports_qcow2_zstd_compression()
iotests/065: Check for zstd support
iotests/303: Check for zstd support
tests/qemu-iotests/065 | 24 ++++++++++++++++++------
tests/qemu-iotests/303 | 4 +++-
tests/qemu-iotests/iotests.py | 20 ++++++++++++++++++++
3 files changed, 41 insertions(+), 7 deletions(-)
--
2.35.1
next reply other threads:[~2022-03-23 10:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-23 10:55 Hanna Reitz [this message]
2022-03-23 10:55 ` [PATCH v3 1/3] iotests.py: Add supports_qcow2_zstd_compression() Hanna Reitz
2022-03-23 11:47 ` Vladimir Sementsov-Ogievskiy
2022-03-23 10:55 ` [PATCH v3 2/3] iotests/065: Check for zstd support Hanna Reitz
2022-03-23 11:48 ` Vladimir Sementsov-Ogievskiy
2022-03-23 10:55 ` [PATCH v3 3/3] iotests/303: " Hanna Reitz
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=20220323105522.53660-1-hreitz@redhat.com \
--to=hreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=v.sementsov-og@mail.ru \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.