From: Avi Kivity <avi@redhat.com>
To: dlaor@redhat.com
Cc: qemu-devel@nongnu.org, kvm-devel <kvm@vger.kernel.org>,
Juan Quintela <quintela@redhat.com>
Subject: [Qemu-devel] Re: KVM call agenda for Nov 30
Date: Tue, 30 Nov 2010 15:35:11 +0200 [thread overview]
Message-ID: <4CF4FD8F.1050801@redhat.com> (raw)
In-Reply-To: <4CF4F504.10208@redhat.com>
On 11/30/2010 02:58 PM, Dor Laor wrote:
> Please send in any agenda items you are interested in covering.
>
nested vmx? must pick up pace if want to merge.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2010-12-01 4:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-22 13:38 [Qemu-devel] KVM call agenda for Nov 23 Juan Quintela
2010-11-22 13:55 ` [Qemu-devel] " Stefan Hajnoczi
2010-11-23 14:37 ` Kevin Wolf
2010-11-23 14:53 ` Stefan Hajnoczi
2010-11-24 10:28 ` Kevin Wolf
2010-11-22 21:45 ` [Qemu-devel] " Chris Wright
2010-11-22 22:53 ` Anthony Liguori
2010-11-22 23:00 ` Anthony Liguori
2010-11-23 12:08 ` Luiz Capitulino
2010-11-23 12:50 ` Michael Tokarev
2010-11-30 12:58 ` [Qemu-devel] KVM call agenda for Nov 30 Dor Laor
2010-11-30 13:30 ` [Qemu-devel] " Stefan Hajnoczi
2010-11-30 13:35 ` 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=4CF4FD8F.1050801@redhat.com \
--to=avi@redhat.com \
--cc=dlaor@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@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 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).