From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Chris Wright <chrisw@redhat.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: KVM call minutes for Mar 8
Date: Tue, 08 Mar 2011 19:45:44 +0200 [thread overview]
Message-ID: <4D766B48.1040002@redhat.com> (raw)
In-Reply-To: <4D766AD4.5090606@siemens.com>
On 03/08/2011 07:43 PM, Jan Kiszka wrote:
> >
> > Something else - 27f368604a3d27ca4d.
>
> I already thought so. But that is understood, fixed, and will be
> obsoleted by the merge.
Ok, will look at your new stuff.
> More interesting are open issues. Any news from that front?
>
None known.
--
error compiling committee.c: too many arguments to function
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Chris Wright <chrisw@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: [Qemu-devel] Re: KVM call minutes for Mar 8
Date: Tue, 08 Mar 2011 19:45:44 +0200 [thread overview]
Message-ID: <4D766B48.1040002@redhat.com> (raw)
In-Reply-To: <4D766AD4.5090606@siemens.com>
On 03/08/2011 07:43 PM, Jan Kiszka wrote:
> >
> > Something else - 27f368604a3d27ca4d.
>
> I already thought so. But that is understood, fixed, and will be
> obsoleted by the merge.
Ok, will look at your new stuff.
> More interesting are open issues. Any news from that front?
>
None known.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-03-08 17:45 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-08 15:50 KVM call minutes for Mar 8 Chris Wright
2011-03-08 15:50 ` [Qemu-devel] " Chris Wright
2011-03-08 16:00 ` Anthony Liguori
2011-03-08 16:00 ` Anthony Liguori
2011-03-08 16:09 ` Stefan Hajnoczi
2011-03-08 16:09 ` Stefan Hajnoczi
2011-03-08 16:51 ` Jan Kiszka
2011-03-08 16:51 ` [Qemu-devel] " Jan Kiszka
2011-03-08 16:58 ` Paolo Bonzini
2011-03-08 16:58 ` [Qemu-devel] " Paolo Bonzini
2011-03-08 17:10 ` Jan Kiszka
2011-03-08 17:10 ` [Qemu-devel] " Jan Kiszka
2011-03-08 17:15 ` Paolo Bonzini
2011-03-08 17:15 ` [Qemu-devel] " Paolo Bonzini
2011-03-08 17:21 ` Jan Kiszka
2011-03-08 17:21 ` [Qemu-devel] " Jan Kiszka
2011-03-08 17:40 ` Avi Kivity
2011-03-08 17:40 ` [Qemu-devel] " Avi Kivity
2011-03-08 17:41 ` Avi Kivity
2011-03-08 17:41 ` [Qemu-devel] " Avi Kivity
2011-03-08 17:42 ` Jan Kiszka
2011-03-08 17:42 ` [Qemu-devel] " Jan Kiszka
2011-03-08 17:43 ` Jan Kiszka
2011-03-08 17:43 ` [Qemu-devel] " Jan Kiszka
2011-03-08 17:45 ` Avi Kivity [this message]
2011-03-08 17:45 ` Avi Kivity
2011-03-15 3:38 ` Marcelo Tosatti
2011-03-15 3:38 ` [Qemu-devel] " Marcelo Tosatti
2011-03-15 7:13 ` Jan Kiszka
2011-03-15 7:13 ` [Qemu-devel] " Jan Kiszka
2011-03-09 9:25 ` [Qemu-devel] " Kevin Wolf
2011-03-09 9:25 ` Kevin Wolf
2011-03-09 13:13 ` Anthony Liguori
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=4D766B48.1040002@redhat.com \
--to=avi@redhat.com \
--cc=chrisw@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=pbonzini@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.