From: Carsten Otte <cotte@de.ibm.com>
To: Avi Kivity <avi@redhat.com>
Cc: borntrae@linux.vnet.ibm.com,
Marcelo Tosatti <mtosatti@redhat.com>,
Alexander Graf <agraf@suse.de>,
heicars2@linux.vnet.ibm.com, KVM list <kvm@vger.kernel.org>,
mschwid2@linux.vnet.ibm.com
Subject: Re: RFC: s390: extension capability for new address space layout
Date: Tue, 20 Sep 2011 16:31:19 +0200 [thread overview]
Message-ID: <4E78A3B7.9070001@de.ibm.com> (raw)
In-Reply-To: <4E788304.2050008@redhat.com>
On 20.09.2011 14:11, Avi Kivity wrote:
> ACK, with Alex's changes. Why are kvm changes not going in through the
> kvm tree? Or at least kvm@ review?
It slipped through as I've put it into our CVS to test against Martin's
changes. Sorry about that, we'll make sure it won't happen again.
so long,
Carsten
prev parent reply other threads:[~2011-09-20 12:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-20 11:56 RFC: s390: extension capability for new address space layout Christian Borntraeger
2011-09-20 12:00 ` Alexander Graf
2011-09-20 12:10 ` Christian Borntraeger
2011-09-20 12:11 ` Avi Kivity
2011-09-20 14:31 ` Carsten Otte [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=4E78A3B7.9070001@de.ibm.com \
--to=cotte@de.ibm.com \
--cc=agraf@suse.de \
--cc=avi@redhat.com \
--cc=borntrae@linux.vnet.ibm.com \
--cc=heicars2@linux.vnet.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=mschwid2@linux.vnet.ibm.com \
--cc=mtosatti@redhat.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