From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: mtosatti@redhat.com, qemu-devel@nongnu.org,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [mst@redhat.com: [PATCHv2 0/3] qemu: memory notifiers]
Date: Thu, 14 Jan 2010 16:33:45 +0200 [thread overview]
Message-ID: <4B4F2B49.2040704@redhat.com> (raw)
In-Reply-To: <4B4F29DF.8060307@codemonkey.ws>
On 01/14/2010 04:27 PM, Anthony Liguori wrote:
> On 01/14/2010 03:32 AM, Michael S. Tsirkin wrote:
>> Avi, Marcelo, if there are no objections, maybe this series can be
>> merged through the new shiny qemu-kvm upstream branch? Thanks!
>
> FWIW, I've been waiting for at least a comment from Avi since that was
> requested in the original post.
Yeah, sorry, I'm behind due to my fpu patchset being subtly broken.
Will flush the queue as I think I have things under control now.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2010-01-14 14:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-14 9:32 [Qemu-devel] [mst@redhat.com: [PATCHv2 0/3] qemu: memory notifiers] Michael S. Tsirkin
2010-01-14 14:27 ` Anthony Liguori
2010-01-14 14:33 ` Avi Kivity [this message]
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=4B4F2B49.2040704@redhat.com \
--to=avi@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=mst@redhat.com \
--cc=mtosatti@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 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.