public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Christian Bornträger" <borntraeger@de.ibm.com>
To: Avi Kivity <avi@redhat.com>
Cc: Carsten Otte <cotte@de.ibm.com>,
	Heiko Carstens <heiko.carstens@de.ibm.com>,
	Martin Schwidefsky <schwidefsky@de.ibm.com>,
	KVM <kvm@vger.kernel.org>
Subject: Re: [patch 0/3] fixes for kvm on s390
Date: Wed, 24 Jun 2009 10:18:37 +0200	[thread overview]
Message-ID: <200906241018.37507.borntraeger@de.ibm.com> (raw)
In-Reply-To: <4A41DF2E.3080908@redhat.com>

Am Mittwoch 24 Juni 2009 10:09:18 schrieben Sie:
> On 06/23/2009 06:24 PM, Christian Borntraeger wrote:
> > Hello Avi,
> >
> > here are three patches against kvm.git that fix several issues in our
> > kvm port. Please review and consider all patches for 2.6.31.
>
> Applied all, and queued the stfle patch for 2.6.31.  The commits
> referenced in patch 1 and 3 doesn't exist in 2.6.31.  Please correct me
> if I misread things.

Yes, the stfle issue is present on linus git and should go to Linus.

Fixes 1 and 3 are only for your kvm.git-tree. They should go to Linus in as soon 
as you push the referenced commits to Linus.

Christian

  reply	other threads:[~2009-06-24  8:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-23 15:24 [patch 0/3] fixes for kvm on s390 Christian Borntraeger
2009-06-23 15:24 ` [patch 1/3] kvm-s390: Fix memslot initialization for userspace_addr != 0 Christian Borntraeger
2009-06-23 15:24 ` [patch 2/3] kvm-s390: Allow stfle instruction in the guest Christian Borntraeger
2009-06-23 15:24 ` [patch 3/3] kvm-s390: Remove some unused variables Christian Borntraeger
2009-06-24  8:09 ` [patch 0/3] fixes for kvm on s390 Avi Kivity
2009-06-24  8:18   ` Christian Bornträger [this message]
2009-06-24  9:18     ` Avi Kivity
2009-06-24  9:23       ` Christian Bornträger

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=200906241018.37507.borntraeger@de.ibm.com \
    --to=borntraeger@de.ibm.com \
    --cc=avi@redhat.com \
    --cc=cotte@de.ibm.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=kvm@vger.kernel.org \
    --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