From: Avi Kivity <avi@qumranet.com>
To: carsteno@de.ibm.com
Cc: carsteno@linux.vnet.ibm.com,
"kvm-devel@lists.sourceforge.net"
<kvm-devel@lists.sourceforge.net>,
Linux-kernel@vger.kernel.org
Subject: Re: [kvm-devel] severe bug in 2.6.23+ kvm.git
Date: Mon, 22 Oct 2007 13:48:56 +0200 [thread overview]
Message-ID: <471C8E28.9020707@qumranet.com> (raw)
In-Reply-To: <471C821A.8020500@de.ibm.com>
Carsten Otte wrote:
> Avi Kivity wrote:
>> kvm.git is actually 2.6.24-rc, pulled from -linus at a random point in
>> time, so it's not at all surprising if something is broken.
> Right. We have a backup now, so next time we'll be ok ;-). Would you
> please pull from Linus again to get the fix into kvm.git so that we
> can use your tree on that machine again?
>
I pulled yesterday so it should be all right (and you don't need me for
that; you can pull from Linus on top of kvm.git).
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2007-10-22 11:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-19 11:22 severe bug in 2.6.23+ kvm.git Carsten Otte
2007-10-19 11:31 ` [kvm-devel] " Aurelien Jarno
2007-10-19 11:37 ` Carsten Otte
2007-10-19 11:42 ` Laurent Vivier
2007-10-19 11:49 ` Carsten Otte
2007-10-19 11:53 ` Laurent Vivier
2007-10-19 11:58 ` Christian Borntraeger
2007-10-19 11:57 ` Mike Lampard
2007-10-19 12:21 ` Carsten Otte
2007-10-19 13:44 ` Carsten Otte
2007-10-19 14:18 ` Jan Engelhardt
2007-10-19 14:48 ` Christian Borntraeger
2007-10-19 14:57 ` Laurent Vivier
2007-10-19 15:23 ` Christian Borntraeger
2007-10-19 15:43 ` Luca Tettamanti
2007-10-19 18:49 ` Christian Borntraeger
2007-10-19 11:55 ` Carsten Otte
2007-10-19 15:13 ` [kvm-devel] " Avi Kivity
2007-10-22 10:57 ` Carsten Otte
2007-10-22 11:48 ` Avi Kivity [this message]
2007-10-22 13:14 ` Carsten Otte
2007-10-22 14:00 ` Carsten Otte
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=471C8E28.9020707@qumranet.com \
--to=avi@qumranet.com \
--cc=Linux-kernel@vger.kernel.org \
--cc=carsteno@de.ibm.com \
--cc=carsteno@linux.vnet.ibm.com \
--cc=kvm-devel@lists.sourceforge.net \
/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