qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: gaowanlong@cn.fujitsu.com
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	Anthony Liguori <aliguori@us.ibm.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/8] OptsVisitor: support / flatten integer ranges for repeating options
Date: Mon, 29 Jul 2013 13:30:18 +0200	[thread overview]
Message-ID: <51F6524A.2070103@redhat.com> (raw)
In-Reply-To: <51F64DEE.3070402@cn.fujitsu.com>

On 07/29/13 13:11, Wanlong Gao wrote:
> On 07/29/2013 07:01 PM, Paolo Bonzini wrote:
>> Il 29/07/2013 11:47, Laszlo Ersek ha scritto:
>>> On 07/22/13 23:07, Laszlo Ersek wrote:
>>>> rfc->v1:
>>>> - addressed Paolo's comments for patches 1 and 2,
>>>> - patches 7 and 8 are new (unit tests),
>>>> - updated the cover letter to take native lists into account, plus
>>>>   cleaned it up.
>>>
>>> Will this be considered for 1.7?
>>
>> Yes, why not? :)
> 
> Nice, I'm rebasing my NUMA patch set on this series.

Thank you, that's most appreciated. I didn't want to ask for it, but I
*have* learned that the best way to sneak in utility stuff is to base
new features on them :)

(This is how OptsVisitor had gotten in originally BTW; Stefan was
working on new network stuff (VLANs vs. hubs IIRC) and he (supposedly)
didn't want to wait too long for my series that introduced OptsVisitor
and also rebased net option parsing to it (his series was modifying net
code too, obviously), so he just applied my stuff :))

Laszlo

  reply	other threads:[~2013-07-29 12:24 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-22 21:07 [Qemu-devel] [PATCH 0/8] OptsVisitor: support / flatten integer ranges for repeating options Laszlo Ersek
2013-07-22 21:07 ` [Qemu-devel] [PATCH 1/8] OptsVisitor: introduce basic list modes Laszlo Ersek
2013-07-22 21:07 ` [Qemu-devel] [PATCH 2/8] OptsVisitor: introduce list modes for interval flattening Laszlo Ersek
2013-07-22 21:07 ` [Qemu-devel] [PATCH 3/8] OptsVisitor: opts_type_int(): recognize intervals when LM_IN_PROGRESS Laszlo Ersek
2013-07-22 21:07 ` [Qemu-devel] [PATCH 4/8] OptsVisitor: rebase opts_type_uint64() to parse_uint_full() Laszlo Ersek
2013-07-22 21:07 ` [Qemu-devel] [PATCH 5/8] OptsVisitor: opts_type_uint64(): recognize intervals when LM_IN_PROGRESS Laszlo Ersek
2013-07-22 21:07 ` [Qemu-devel] [PATCH 6/8] OptsVisitor: don't try to flatten overlong integer ranges Laszlo Ersek
2013-07-22 21:07 ` [Qemu-devel] [PATCH 7/8] add "test-int128" to .gitignore Laszlo Ersek
2013-07-22 21:07 ` [Qemu-devel] [PATCH 8/8] OptsVisitor: introduce unit tests, with test cases for range flattening Laszlo Ersek
2013-07-22 22:04   ` Eric Blake
2013-07-22 22:24     ` Laszlo Ersek
2013-07-22 22:26       ` Eric Blake
2013-07-22 22:37         ` Laszlo Ersek
2013-08-19 19:26   ` Luiz Capitulino
2013-08-19 19:55     ` Laszlo Ersek
2013-08-19 20:04       ` Laszlo Ersek
2013-07-29  9:47 ` [Qemu-devel] [PATCH 0/8] OptsVisitor: support / flatten integer ranges for repeating options Laszlo Ersek
2013-07-29 11:01   ` Paolo Bonzini
2013-07-29 11:11     ` Wanlong Gao
2013-07-29 11:30       ` Laszlo Ersek [this message]
2013-08-16  7:15 ` Laszlo Ersek

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=51F6524A.2070103@redhat.com \
    --to=lersek@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=gaowanlong@cn.fujitsu.com \
    --cc=pbonzini@redhat.com \
    --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).