From: Jeff Cody <jcody@redhat.com>
To: qemu-devel@nongnu.org
Cc: qemu-block@nongnu.org, kwolf@redhat.com, mreitz@redhat.com,
eblake@redhat.com
Subject: [Qemu-devel] [PATCH v2 0/3] block: check full backing filename when searching protocol filenames
Date: Wed, 25 Jan 2017 20:08:19 -0500 [thread overview]
Message-ID: <cover.1485392617.git.jcody@redhat.com> (raw)
Differences from v1:
Patch 1: set local_error = NULL after freeing (Thanks Eric)
Patch 2: new patch, groundwork for qemu-iotest in patch 3
Patch 3: qemu-iotest, as requested (Thanks Max)
Jeff Cody (3):
block: check full backing filename when searching protocol filenames
qemu-iotests: Don't create fifos / pidfiles with protocol paths
qemu-iotest: test to lookup protocol-based image with relative backing
block.c | 13 ++++++
tests/qemu-iotests/173 | 97 ++++++++++++++++++++++++++++++++++++++++
tests/qemu-iotests/173.out | 12 +++++
tests/qemu-iotests/common.config | 6 ++-
tests/qemu-iotests/common.qemu | 10 ++---
tests/qemu-iotests/common.rc | 6 +--
tests/qemu-iotests/group | 1 +
7 files changed, 135 insertions(+), 10 deletions(-)
create mode 100755 tests/qemu-iotests/173
create mode 100644 tests/qemu-iotests/173.out
--
2.9.3
next reply other threads:[~2017-01-26 1:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-26 1:08 Jeff Cody [this message]
2017-01-26 1:08 ` [Qemu-devel] [PATCH v2 1/3] block: check full backing filename when searching protocol filenames Jeff Cody
2017-01-26 1:08 ` [Qemu-devel] [PATCH v2 2/3] qemu-iotests: Don't create fifos / pidfiles with protocol paths Jeff Cody
2017-01-26 1:08 ` [Qemu-devel] [PATCH v2 3/3] qemu-iotest: test to lookup protocol-based image with relative backing Jeff Cody
2017-02-01 2:43 ` [Qemu-devel] [PATCH v2 0/3] block: check full backing filename when searching protocol filenames Max 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=cover.1485392617.git.jcody@redhat.com \
--to=jcody@redhat.com \
--cc=eblake@redhat.com \
--cc=kwolf@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).