From: Max Reitz <mreitz@redhat.com>
To: qemu-block@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, John Snow <jsnow@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 0/7] vmdk: Misc fixes
Date: Tue, 27 Aug 2019 19:16:33 +0200 [thread overview]
Message-ID: <f5caf55b-a5be-64b9-c341-b77b5ace4369@redhat.com> (raw)
In-Reply-To: <20190815153638.4600-1-mreitz@redhat.com>
[-- Attachment #1.1: Type: text/plain, Size: 452 bytes --]
On 15.08.19 17:36, Max Reitz wrote:
> I made the mistake of trying to run the iotests with all non-default
> subformats our vmdk driver has to offer:
> - monolithicFlat
> - twoGbMaxExtentSparse
> - twoGbMaxExtentFlat
> - streamOptimized
>
> Many things broke, so this series fixes what I found. It’s mostly just
> iotest fixes, but there are actually two real fixes in here.
Thanks for the review, applied to my block branch.
Max
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2019-08-27 17:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-15 15:36 [Qemu-devel] [PATCH v2 0/7] vmdk: Misc fixes Max Reitz
2019-08-15 15:36 ` [Qemu-devel] [PATCH v2 1/7] iotests: Fix _filter_img_create() Max Reitz
2019-08-15 15:36 ` [Qemu-devel] [PATCH v2 2/7] vmdk: Use bdrv_dirname() for relative extent paths Max Reitz
2019-08-15 15:36 ` [Qemu-devel] [PATCH v2 3/7] iotests: Keep testing broken " Max Reitz
2019-08-15 15:36 ` [Qemu-devel] [PATCH v2 4/7] vmdk: Reject invalid compressed writes Max Reitz
2019-08-15 15:36 ` [Qemu-devel] [PATCH v2 5/7] iotests: Disable broken streamOptimized tests Max Reitz
2019-08-15 15:36 ` [Qemu-devel] [PATCH v2 6/7] iotests: Disable 110 for vmdk.twoGbMaxExtentSparse Max Reitz
2019-08-15 15:36 ` [Qemu-devel] [PATCH v2 7/7] iotests: Disable 126 for flat vmdk subformats Max Reitz
2019-08-15 21:20 ` [Qemu-devel] [PATCH v2 0/7] vmdk: Misc fixes John Snow
2019-08-27 17:16 ` Max 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=f5caf55b-a5be-64b9-c341-b77b5ace4369@redhat.com \
--to=mreitz@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--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).