From: Avi Kivity <avi@qumranet.com>
To: Carsten Otte <cotte@de.ibm.com>
Cc: Christian Borntraeger <borntraeger@de.ibm.com>,
heicars2 <heicars2@linux.vnet.ibm.com>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Olaf Schnapper <os@de.ibm.com>,
"kvm-devel@lists.sourceforge.net" <kvm@vger.kernel.org>
Subject: Re: [BUGFIX/PATCH 0/6] kvm-s390 fixes
Date: Thu, 22 May 2008 12:20:57 +0300 [thread overview]
Message-ID: <48353AF9.8040600@qumranet.com> (raw)
In-Reply-To: <1211369829.6194.10.camel@cotte.boeblingen.de.ibm.com>
Carsten Otte wrote:
> Hi Avi,
>
> this series contains a few Bug fixes of issues that we've identified. I
> consider them all safe for 2.6.26, and in fact some of them fix serious
> issues in the current upstream code.
>
>
Applied and queued all. Martin, can you ack patch 2, which is in s390
code, not kvm code (although it is only triggered when kvm is invoked
AFAICT).
--
error compiling committee.c: too many arguments to function
next parent reply other threads:[~2008-05-22 9:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1211369829.6194.10.camel@cotte.boeblingen.de.ibm.com>
2008-05-22 9:20 ` Avi Kivity [this message]
2008-05-23 10:51 ` [BUGFIX/PATCH 0/6] kvm-s390 fixes Martin Schwidefsky
2008-05-25 13:47 ` 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=48353AF9.8040600@qumranet.com \
--to=avi@qumranet.com \
--cc=borntraeger@de.ibm.com \
--cc=cotte@de.ibm.com \
--cc=heicars2@linux.vnet.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=os@de.ibm.com \
--cc=schwidefsky@de.ibm.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