From: Eric Blake <eblake@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: kwolf@redhat.com, Dong Xu Wang <wdongxu@linux.vnet.ibm.com>,
wdongxu@cn.ibm.com, qemu-devel@nongnu.org, armbru@redhat.com,
stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH V16 0/7] replace QEMUOptionParameter with QemuOpts parser
Date: Tue, 09 Jul 2013 14:41:46 -0600 [thread overview]
Message-ID: <51DC758A.8020200@redhat.com> (raw)
In-Reply-To: <20130704125243.GE4213@stefanha-thinkpad.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1169 bytes --]
On 07/04/2013 06:52 AM, Stefan Hajnoczi wrote:
> On Tue, Jun 18, 2013 at 05:31:52PM +0800, Dong Xu Wang wrote:
>> These patches will replace QEMUOptionParameter with QemuOpts. Change logs
>> please go to each patch's commit message.
>>
>> Dong Xu Wang (7):
>> add def_value_str in QemuOptDesc struct and rewrite qemu_opts_print
>> avoid duplication of default value in QemuOpts
>> Create four QemuOptsList related functions
>> Create some QemuOpts functons
>> Use QemuOpts support in block layer
>> query-command-line-options outputs def_value_str
>> remove QEMUOptionParameter related functions and struct
>>
>> V15->V16:
>> 1) discard double-initialization.
>> 2) use pointer directly, not g_strdup.
>> 3) modify query-command-line-options related code.
>> V14->V15:
>> 1) Only delete enum QEMUOptionParType.
>
> eblake: You commented on the last revision. Are you happy with v16?
Apologies for my delays (still digging myself out of 3 weeks
accumulation of mail after my vacation); I'll review within 24 hours.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 621 bytes --]
next prev parent reply other threads:[~2013-07-09 20:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-18 9:31 [Qemu-devel] [PATCH V16 0/7] replace QEMUOptionParameter with QemuOpts parser Dong Xu Wang
2013-06-18 9:31 ` [Qemu-devel] [PATCH V16 1/7] add def_value_str in QemuOptDesc struct and rewrite qemu_opts_print Dong Xu Wang
2013-06-18 9:31 ` [Qemu-devel] [PATCH V16 2/7] avoid duplication of default value in QemuOpts Dong Xu Wang
2013-06-18 9:31 ` [Qemu-devel] [PATCH V16 3/7] Create four QemuOptsList related functions Dong Xu Wang
2013-07-10 16:07 ` Eric Blake
2013-06-18 9:31 ` [Qemu-devel] [PATCH V16 4/7] Create some QemuOpts functons Dong Xu Wang
2013-07-10 16:51 ` Eric Blake
2013-07-10 19:06 ` Eric Blake
2013-06-18 9:31 ` [Qemu-devel] [PATCH V16 5/7] Use QemuOpts support in block layer Dong Xu Wang
2013-07-10 17:56 ` Eric Blake
2013-07-10 19:47 ` Eric Blake
2013-06-18 9:31 ` [Qemu-devel] [PATCH V16 6/7] query-command-line-options outputs def_value_str Dong Xu Wang
2013-07-10 19:56 ` Eric Blake
2013-06-18 9:31 ` [Qemu-devel] [PATCH V16 7/7] remove QEMUOptionParameter related functions and struct Dong Xu Wang
2013-07-10 19:57 ` Eric Blake
2013-07-04 12:52 ` [Qemu-devel] [PATCH V16 0/7] replace QEMUOptionParameter with QemuOpts parser Stefan Hajnoczi
2013-07-09 20:41 ` Eric Blake [this message]
2013-07-10 19:49 ` Eric Blake
2013-07-15 7:38 ` Dong Xu Wang
2013-07-09 22:05 ` Andreas Färber
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=51DC758A.8020200@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=stefanha@redhat.com \
--cc=wdongxu@cn.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.