From: Avi Kivity <avi@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: Carsten Otte <cotte@de.ibm.com>,
carsteno@linux.vnet.ibm.com, KVM list <kvm@vger.kernel.org>,
Carsten Otte <carsteno@de.ibm.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
hare@suse.de
Subject: [Qemu-devel] Re: [PATCH 0/9] S390x KVM support
Date: Tue, 03 Nov 2009 10:55:06 +0200 [thread overview]
Message-ID: <4AEFEFEA.9080205@redhat.com> (raw)
In-Reply-To: <4AEF3FA6.9050301@suse.de>
On 11/02/2009 10:23 PM, Alexander Graf wrote:
> Any progress on the patch? This is really important to make KVM work
> properly on S390. I'd even go as far as suggesting it for linux-stable.
>
>
I forgot all about it, sorry. Marcelo, can you commit it?
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-11-03 8:55 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-19 14:37 [Qemu-devel] [PATCH 0/9] S390x KVM support Alexander Graf
2009-10-19 14:37 ` [Qemu-devel] [PATCH 1/9] Export function for VA defined ram allocation Alexander Graf
2009-10-19 14:37 ` [Qemu-devel] [PATCH 2/9] Add KVM support for S390x Alexander Graf
2009-10-19 14:37 ` [Qemu-devel] [PATCH 3/9] Add support for S390x system emulation Alexander Graf
2009-10-19 14:37 ` [Qemu-devel] [PATCH 4/9] Add S390x virtio machine bus Alexander Graf
2009-10-19 14:37 ` [Qemu-devel] [PATCH 5/9] Add S390x virtio machine description Alexander Graf
2009-10-19 14:37 ` [Qemu-devel] [PATCH 6/9] S390 GDB stub Alexander Graf
2009-10-19 14:37 ` [Qemu-devel] [PATCH 7/9] Implement early printk in virtio-console Alexander Graf
2009-10-19 14:37 ` [Qemu-devel] [PATCH 8/9] Set default console to virtio on S390x Alexander Graf
2009-10-19 14:37 ` [Qemu-devel] [PATCH 9/9] Move mp_state to CPU_COMMON Alexander Graf
2009-10-19 19:48 ` [Qemu-devel] [PATCH 8/9] Set default console to virtio on S390x Gerd Hoffmann
2009-10-19 19:34 ` [Qemu-devel] [PATCH 4/9] Add S390x virtio machine bus Gerd Hoffmann
2009-10-19 19:40 ` Alexander Graf
2009-10-19 20:10 ` Gerd Hoffmann
2009-10-20 8:36 ` [Qemu-devel] Re: [PATCH 2/9] Add KVM support for S390x Carsten Otte
2009-10-20 8:41 ` Alexander Graf
2009-10-20 8:02 ` [Qemu-devel] Re: [PATCH 1/9] Export function for VA defined ram allocation Carsten Otte
2009-10-19 19:24 ` [Qemu-devel] [PATCH 0/9] S390x KVM support Gerd Hoffmann
2009-10-19 19:32 ` Alexander Graf
2009-10-20 5:05 ` Avi Kivity
2009-10-20 16:40 ` [Qemu-devel] " Carsten Otte
2009-10-21 7:20 ` Alexander Graf
2009-10-21 7:24 ` Alexander Graf
2009-10-21 8:18 ` Carsten Otte
2009-10-21 8:23 ` Alexander Graf
2009-10-21 7:26 ` Alexander Graf
2009-10-22 9:08 ` Avi Kivity
2009-10-22 9:11 ` Alexander Graf
2009-10-22 9:53 ` Avi Kivity
2009-10-22 9:55 ` Alexander Graf
2009-10-22 9:58 ` Alexander Graf
2009-10-22 10:03 ` Avi Kivity
2009-10-22 10:13 ` Alexander Graf
2009-10-22 10:22 ` Carsten Otte
2009-10-22 10:28 ` Avi Kivity
2009-10-22 10:43 ` Carsten Otte
2009-10-22 10:49 ` Avi Kivity
2009-10-22 11:10 ` Carsten Otte
2009-11-02 20:23 ` Alexander Graf
2009-11-03 8:55 ` Avi Kivity [this message]
2009-10-22 9:18 ` Carsten Otte
2009-10-22 10:02 ` Avi Kivity
2009-10-22 10:20 ` Carsten Otte
2009-10-22 10:29 ` 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=4AEFEFEA.9080205@redhat.com \
--to=avi@redhat.com \
--cc=agraf@suse.de \
--cc=carsteno@de.ibm.com \
--cc=carsteno@linux.vnet.ibm.com \
--cc=cotte@de.ibm.com \
--cc=hare@suse.de \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).