From: Stefan Hajnoczi <stefanha@gmail.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org, Kevin Wolf <kwolf@redhat.com>,
qemu-block@nongnu.org, Max Reitz <mreitz@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Fam Zheng <famz@redhat.com>
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH 2/2] iotests: blacklist 194 with the luks driver
Date: Tue, 5 Sep 2017 11:04:04 +0100 [thread overview]
Message-ID: <20170905100404.GH17449@stefanha-x1.localdomain> (raw)
In-Reply-To: <20170901105434.3288-3-berrange@redhat.com>
On Fri, Sep 01, 2017 at 11:54:34AM +0100, Daniel P. Berrange wrote:
> The 194 test has alot of code that assumes a simple image file. Rewriting
> this to work with luks is possible, but non-trivial, so blacklist the
> luks format for now.
>
> Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
> ---
> tests/qemu-iotests/194 | 1 +
> tests/qemu-iotests/iotests.py | 4 +++-
> 2 files changed, 4 insertions(+), 1 deletion(-)
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
next prev parent reply other threads:[~2017-09-05 10:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-01 10:54 [Qemu-devel] [PATCH 0/2] Fix / skip recent iotests with LUKS driver Daniel P. Berrange
2017-09-01 10:54 ` [Qemu-devel] [PATCH 1/2] iotests: rewrite 192 to use _launch_qemu to fix LUKS support Daniel P. Berrange
2017-09-01 14:22 ` Eric Blake
2017-09-05 9:29 ` Kevin Wolf
2017-09-01 10:54 ` [Qemu-devel] [PATCH 2/2] iotests: blacklist 194 with the luks driver Daniel P. Berrange
2017-09-01 14:25 ` Eric Blake
2017-09-04 9:14 ` [Qemu-devel] [Qemu-block] " Kashyap Chamarthy
2017-09-05 10:04 ` Stefan Hajnoczi [this message]
2017-09-01 14:26 ` [Qemu-devel] [PATCH 0/2] Fix / skip recent iotests with LUKS driver Eric Blake
2017-09-01 14:33 ` Daniel P. Berrange
2017-09-01 20:10 ` Eric Blake
2017-09-01 14:55 ` Fam Zheng
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=20170905100404.GH17449@stefanha-x1.localdomain \
--to=stefanha@gmail.com \
--cc=berrange@redhat.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).