From: Kevin Wolf <kwolf@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Dong Xu Wang <wdongxu@linux.vnet.ibm.com>,
qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH V12 0/4] replace QEMUOptionParameter with QemuOpts parser
Date: Thu, 21 Mar 2013 14:20:20 +0100 [thread overview]
Message-ID: <20130321132019.GD2726@dhcp-200-207.str.redhat.com> (raw)
In-Reply-To: <87vc8koqfc.fsf@blackfin.pond.sub.org>
Am 21.03.2013 um 14:03 hat Markus Armbruster geschrieben:
> Doesn't apply anymore. I'll review anyway; sorry for being late with
> that.
>
> Kevin, I haven't been able to follow your work on driver-specific
> options; do you expect further conflicts with this work?
No, QEMUOptionParameter is only used for bdrv_create(), i.e. creating
images, which I don't touch. In my work on bdrv_open() I've been using
QDict/QemuOpts from the beginning.
Kevin
next prev parent reply other threads:[~2013-03-21 13:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1362043236-4635-1-git-send-email-wdongxu@linux.vnet.ibm.com>
2013-03-05 9:06 ` [Qemu-devel] [PATCH V12 0/4] replace QEMUOptionParameter with QemuOpts parser Stefan Hajnoczi
2013-03-07 7:36 ` Markus Armbruster
2013-03-21 13:03 ` Markus Armbruster
2013-03-21 13:20 ` Kevin Wolf [this message]
[not found] ` <1362043236-4635-3-git-send-email-wdongxu@linux.vnet.ibm.com>
2013-03-21 13:05 ` [Qemu-devel] [PATCH V12 2/4] Create four QemuOptsList related functions Markus Armbruster
[not found] ` <1362043236-4635-4-git-send-email-wdongxu@linux.vnet.ibm.com>
2013-03-06 1:51 ` [Qemu-devel] [PATCH V12 3/4] Use QemuOpts support in block layer Dong Xu Wang
2013-03-21 15:31 ` Markus Armbruster
2013-03-25 6:31 ` Dong Xu Wang
2013-04-02 16:22 ` Markus Armbruster
[not found] ` <1362043236-4635-2-git-send-email-wdongxu@linux.vnet.ibm.com>
2013-03-21 15:59 ` [Qemu-devel] [PATCH V12 1/4] add def_value_str and use it in qemu_opts_print Markus Armbruster
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=20130321132019.GD2726@dhcp-200-207.str.redhat.com \
--to=kwolf@redhat.com \
--cc=armbru@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=wdongxu@linux.vnet.ibm.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).