From: Kevin Wolf <kwolf@redhat.com>
To: Jeff Cody <jcody@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org, mreitz@redhat.com
Subject: Re: [Qemu-devel] [PATCH 0/2] qemu-iotest tweaks
Date: Tue, 14 Feb 2017 20:05:14 +0100 [thread overview]
Message-ID: <20170214190514.GD6189@noname.redhat.com> (raw)
In-Reply-To: <cover.1487088544.git.jcody@redhat.com>
Am 14.02.2017 um 17:21 hat Jeff Cody geschrieben:
> Some minor qemu-iotest tweaks.
>
> The second patch makes it easier to add some upcoming protocols such as VXHS,
> that do not support .bdrv_create.
Thanks, applied to the block branch.
Kevin
prev parent reply other threads:[~2017-02-14 19:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 16:21 [Qemu-devel] [PATCH 0/2] qemu-iotest tweaks Jeff Cody
2017-02-14 16:21 ` [Qemu-devel] [PATCH 1/2] qemu-iotests: Test 137 only supports 'file' protocol Jeff Cody
2017-02-14 16:21 ` [Qemu-devel] [PATCH 2/2] qemu-iotests: add ability to exclude certain protocols from tests Jeff Cody
2017-02-14 19:05 ` Kevin Wolf [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=20170214190514.GD6189@noname.redhat.com \
--to=kwolf@redhat.com \
--cc=jcody@redhat.com \
--cc=mreitz@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).