From: Avi Kivity <avi@qumranet.com>
To: Carsten Otte <cotte@de.ibm.com>
Cc: Christian Borntraeger <borntraeger@de.ibm.com>,
Olaf Schnapper <os@de.ibm.com>,
schwidefsky@de.ibm.com, kvm <kvm@vger.kernel.org>
Subject: Re: [PATCH 0/4] kvm-s390 patches for 2.6.27
Date: Sun, 29 Jun 2008 15:08:13 +0300 [thread overview]
Message-ID: <48677B2D.8050907@qumranet.com> (raw)
In-Reply-To: <1214571921.5857.17.camel@cotte.boeblingen.de.ibm.com>
Carsten Otte wrote:
> Hi Avi,
>
> now that we're moving closer to the merge window, please look at the
> following patches. I'd love to see them in 2.6.27. There is no need to
> hurry any of these into 2.6.26 because our console patches are waiting
> for the merge window in Rustys queue too, which makes .26 unusable with
> kuli.
>
> [PATCH 1/4] kvm: dont allocate dirty bitmap for s390
> [PATCH 2/4] kvm-s390: Fix memory leak on guest exit
> [PATCH 3/4] kvm-s390: Set guest storage limit and offset to sane values
> [PATCH 4/4] kvm-s390: rename private structures
>
>
Thanks, all applied.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2008-06-29 12:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-27 13:05 [PATCH 0/4] kvm-s390 patches for 2.6.27 Carsten Otte
2008-06-29 12:08 ` Avi Kivity [this message]
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=48677B2D.8050907@qumranet.com \
--to=avi@qumranet.com \
--cc=borntraeger@de.ibm.com \
--cc=cotte@de.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