From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Chris Wright <chrisw@redhat.com>,
qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: [Qemu-devel] Re: KVM call agenda for Jan 25
Date: Tue, 25 Jan 2011 16:26:35 +0200 [thread overview]
Message-ID: <4D3EDD9B.5030309@redhat.com> (raw)
In-Reply-To: <4D3DF7EA.4010807@codemonkey.ws>
On 01/25/2011 12:06 AM, Anthony Liguori wrote:
> On 01/24/2011 07:25 AM, Chris Wright wrote:
>> Please send in any agenda items you are interested in covering.
>
> - coroutines for the block layer
I have a perpetually in progress branch for this, and would very much
like to see this done.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-01-25 14:26 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-24 13:25 [Qemu-devel] KVM call agenda for Jan 25 Chris Wright
2011-01-24 22:06 ` [Qemu-devel] " Anthony Liguori
2011-01-25 13:57 ` Luiz Capitulino
2011-01-25 14:02 ` Luiz Capitulino
2011-01-25 14:13 ` Stefan Hajnoczi
2011-01-29 10:50 ` Dushyant Bansal
2011-01-29 13:16 ` Stefan Hajnoczi
2011-02-25 17:42 ` Dushyant Bansal
2011-02-26 14:05 ` Stefan Hajnoczi
2011-02-26 21:50 ` Dushyant Bansal
2011-02-27 10:49 ` Stefan Hajnoczi
2011-02-28 7:36 ` Markus Armbruster
2011-02-28 20:41 ` Dushyant Bansal
2011-03-01 9:40 ` Stefan Hajnoczi
2011-03-14 15:13 ` Dushyant Bansal
2011-03-15 10:27 ` Kevin Wolf
2011-03-16 14:17 ` Dushyant Bansal
2011-03-16 17:47 ` Stefan Hajnoczi
2011-03-17 10:07 ` Kevin Wolf
2011-03-26 21:56 ` Dushyant Bansal
2011-03-28 10:26 ` Kevin Wolf
2011-01-25 14:11 ` Aurelien Jarno
2011-01-25 14:27 ` Anthony Liguori
2011-01-25 14:42 ` Kevin Wolf
2011-01-25 15:29 ` Aurelien Jarno
2011-01-25 14:26 ` Avi Kivity [this message]
2011-01-25 14:35 ` Stefan Hajnoczi
2011-01-26 9:58 ` Avi Kivity
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=4D3EDD9B.5030309@redhat.com \
--to=avi@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=chrisw@redhat.com \
--cc=kvm@vger.kernel.org \
--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).