From: Hanna Reitz <hreitz@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
qemu-block@nongnu.org
Cc: kwolf@redhat.com, jsnow@redhat.com, qemu-devel@nongnu.org
Subject: Re: [PATCH v5 00/19] iotests: support zstd
Date: Thu, 13 Jan 2022 17:11:21 +0100 [thread overview]
Message-ID: <1faee052-7a31-0506-48ed-874a90b71ea8@redhat.com> (raw)
In-Reply-To: <20211223160144.1097696-1-vsementsov@virtuozzo.com>
On 23.12.21 17:01, Vladimir Sementsov-Ogievskiy wrote:
> These series makes tests pass with
>
> IMGOPTS='compression_type=zstd'
>
> Also, python iotests start to support IMGOPTS (they didn't before).
>
> v5: Move patches with unsupported_imgopts to the start of the series
> 02: add Hanna's r-b
> 03: - don't modify migrate-during-backup test
> - disably any 'compat' instead of just 'compat=0.10'
Thanks!
Applied to my block branch: https://gitlab.com/hreitz/qemu/-/commits/block
prev parent reply other threads:[~2022-01-13 16:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-23 16:01 [PATCH v5 00/19] iotests: support zstd Vladimir Sementsov-Ogievskiy
2021-12-23 16:01 ` [PATCH v5 01/19] iotests.py: img_info_log(): rename imgopts argument Vladimir Sementsov-Ogievskiy
2021-12-23 16:01 ` [PATCH v5 02/19] iotests.py: implement unsupported_imgopts Vladimir Sementsov-Ogievskiy
2021-12-23 16:01 ` [PATCH v5 03/19] iotests: specify some unsupported_imgopts for python iotests Vladimir Sementsov-Ogievskiy
2021-12-23 16:01 ` [PATCH v5 04/19] iotests.py: qemu_img*("create"): support IMGOPTS='compression_type=zstd' Vladimir Sementsov-Ogievskiy
2021-12-23 16:01 ` [PATCH v5 05/19] iotests: drop qemu_img_verbose() helper Vladimir Sementsov-Ogievskiy
2021-12-23 16:01 ` [PATCH v5 06/19] iotests.py: rewrite default luks support in qemu_img Vladimir Sementsov-Ogievskiy
2021-12-23 16:01 ` [PATCH v5 07/19] iotest 303: explicit compression type Vladimir Sementsov-Ogievskiy
2021-12-23 16:01 ` [PATCH v5 08/19] iotest 065: " Vladimir Sementsov-Ogievskiy
2021-12-23 16:01 ` [PATCH v5 09/19] iotests.py: filter out successful output of qemu-img create Vladimir Sementsov-Ogievskiy
2021-12-23 16:01 ` [PATCH v5 10/19] iotests.py: filter compression type out Vladimir Sementsov-Ogievskiy
2021-12-23 16:01 ` [PATCH v5 11/19] iotest 302: use img_info_log() helper Vladimir Sementsov-Ogievskiy
2021-12-23 16:01 ` [PATCH v5 12/19] qcow2: simple case support for downgrading of qcow2 images with zstd Vladimir Sementsov-Ogievskiy
2021-12-23 16:01 ` [PATCH v5 13/19] iotests/common.rc: introduce _qcow2_dump_header helper Vladimir Sementsov-Ogievskiy
2021-12-23 16:01 ` [PATCH v5 14/19] iotests: massive use _qcow2_dump_header Vladimir Sementsov-Ogievskiy
2021-12-23 16:01 ` [PATCH v5 15/19] iotest 39: " Vladimir Sementsov-Ogievskiy
2021-12-23 16:01 ` [PATCH v5 16/19] iotests: bash tests: filter compression type Vladimir Sementsov-Ogievskiy
2021-12-23 16:01 ` [PATCH v5 17/19] iotests 60: more accurate set dirty bit in qcow2 header Vladimir Sementsov-Ogievskiy
2021-12-23 16:01 ` [PATCH v5 18/19] iotest 214: explicit compression type Vladimir Sementsov-Ogievskiy
2021-12-23 16:01 ` [PATCH v5 19/19] iotests: declare lack of support for compresion_type in IMGOPTS Vladimir Sementsov-Ogievskiy
2022-01-13 16:11 ` Hanna Reitz [this message]
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=1faee052-7a31-0506-48ed-874a90b71ea8@redhat.com \
--to=hreitz@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.com \
/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).