From: Jeff Cody <jcody@redhat.com>
To: qemu-devel@nongnu.org
Cc: qemu-block@nongnu.org, kwolf@redhat.com, armbru@redhat.com
Subject: [Qemu-devel] [RFC 0/2] Parse 'filename' option for RBD/iSCSI
Date: Mon, 12 Jun 2017 00:05:12 -0400 [thread overview]
Message-ID: <cover.1497240079.git.jcody@redhat.com> (raw)
We need to be able to parse the 'filename' option for both rbd and iscsi,
because there may exist images in the wild that have json backing files,
that specify the filename argument.
Marking the series as RFC at least partially for the precedence given to
arguments; as written, these patches will give preference to the 'filename'
parameter over passed options.
Jeff Cody (2):
block/rbd: enable filename option and parsing
block/iscsi: enable filename option and parsing
block/iscsi.c | 19 ++++++++++++++++++-
block/rbd.c | 19 ++++++++++++++++++-
2 files changed, 36 insertions(+), 2 deletions(-)
--
2.9.3
next reply other threads:[~2017-06-12 4:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-12 4:05 Jeff Cody [this message]
2017-06-12 4:05 ` [Qemu-devel] [RFC 1/2] block/rbd: enable filename option and parsing Jeff Cody
2017-06-12 4:05 ` [Qemu-devel] [RFC 2/2] block/iscsi: " Jeff Cody
2017-06-12 13:51 ` [Qemu-devel] [RFC 0/2] Parse 'filename' option for RBD/iSCSI Richard W.M. Jones
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.1497240079.git.jcody@redhat.com \
--to=jcody@redhat.com \
--cc=armbru@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).