From: Jan Kiszka <jan.kiszka@siemens.com>
To: quintela@redhat.com
Cc: qemu-devel@nongnu.org, KVM devel mailing list <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] KVM call agenda for May 03rd
Date: Tue, 03 May 2011 15:04:23 +0200 [thread overview]
Message-ID: <4DBFFD57.4070909@siemens.com> (raw)
In-Reply-To: <m3liyo3x0q.fsf@neno.mitica>
On 2011-05-03 12:21, Juan Quintela wrote:
>
> Please send in any agenda items you are interested in covering.
>
Provided there will be more topics:
- import kvm headers into qemu, drop #ifdef maze
Otherwise, we can also discuss this based on the patch I'm preparing ATM.
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2011-05-03 13:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-03 10:21 [Qemu-devel] KVM call agenda for May 03rd Juan Quintela
2011-05-03 13:04 ` Jan Kiszka [this message]
2011-05-03 13:07 ` Anthony Liguori
2011-05-03 14:10 ` Jan Kiszka
2011-05-03 14:02 ` Jes Sorensen
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=4DBFFD57.4070909@siemens.com \
--to=jan.kiszka@siemens.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).