From: Avi Kivity <avi@redhat.com>
To: liu ping fan <qemulist@gmail.com>
Cc: quintela@redhat.com, KVM devel mailing list <kvm@vger.kernel.org>,
virt-devel@redhat.com, Jan Kiszka <jan.kiszka@siemens.com>,
Liu Ping Fan <pingfank@linux.vnet.ibm.com>
Subject: Re: KVM call agenda for Tuesday, September 4th
Date: Tue, 04 Sep 2012 11:21:44 +0300 [thread overview]
Message-ID: <5045BA18.9070703@redhat.com> (raw)
In-Reply-To: <CAJnKYQnX9CNkN3Dp378cviOWY26uT+CGoXZue4SkCMDFG6hLZA@mail.gmail.com>
On 09/04/2012 11:17 AM, liu ping fan wrote:
> On Mon, Sep 3, 2012 at 7:48 PM, Avi Kivity <avi@redhat.com> wrote:
>> On 09/03/2012 09:44 AM, Juan Quintela wrote:
>>>
>>> Hi
>>>
>>> Please send in any agenda items you are interested in covering.
>>
>> - protecting MemoryRegion::opaque during dispatch
>>
>> I'm guessing Ping won't make it due to timezone problems. Jan, if you
>> will not participate, please remove the topic from the list (unless
>> someone else wants to argue your side).
>>
> Is there log for this topic? Link?
The call has not happened yet (it's in 5 hours 40 minutes), but Jan
can't participate, so it will likely be cancelled. If you can
participate, maybe we can have it anyway.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-09-04 8:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-03 6:44 KVM call agenda for Tuesday, September 4th Juan Quintela
2012-09-03 11:43 ` Juan Quintela
2012-09-03 11:43 ` [Qemu-devel] " Juan Quintela
2012-09-03 11:48 ` Avi Kivity
2012-09-03 13:35 ` Jan Kiszka
2012-09-03 14:30 ` Avi Kivity
2012-09-04 13:16 ` Juan Quintela
2012-09-04 13:23 ` Avi Kivity
2012-09-04 8:17 ` liu ping fan
2012-09-04 8:21 ` Avi Kivity [this message]
2012-09-04 8:29 ` liu ping fan
2012-09-04 13:26 ` Juan Quintela
2012-09-04 13:26 ` [Qemu-devel] " Juan Quintela
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=5045BA18.9070703@redhat.com \
--to=avi@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=pingfank@linux.vnet.ibm.com \
--cc=qemulist@gmail.com \
--cc=quintela@redhat.com \
--cc=virt-devel@redhat.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.