public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: Marcelo Tossati <mtosatti@redhat.com>,
	Alexander Graf <agraf@suse.de>,
	Jens Freimann <jfrei@linux.vnet.ibm.com>,
	Cornelia Huck <cornelia.huck@de.ibm.com>,
	Heiko Carstens <heiko.carstens@de.ibm.com>,
	Martin Schwidefsky <schwidefsky@de.ibm.com>,
	KVM <kvm@vger.kernel.org>,
	linux-s390@vger.kernel.org
Subject: Re: [PATCH 0/3] s390/kvm fixes
Date: Tue, 29 Jan 2013 21:41:21 +0100	[thread overview]
Message-ID: <510833F1.2000200@de.ibm.com> (raw)
In-Reply-To: <20130129131202.GC15004@redhat.com>

On 29/01/13 14:12, Gleb Natapov wrote:
> On Fri, Jan 25, 2013 at 03:34:14PM +0100, Christian Borntraeger wrote:
>> Gleb, Marcelo,
>>
> Alex, can you review?

Last time I checked, Cornelia and myself were s390/kvm/kernel maintainers ;-)
Alex is maintainer for s390/kvm/qemu. 
If the patch introduces or touched an kernel<->qemu interface, I usually try
to come to a conclusion with Alex before submission, but these patches are
only bugfixes and Alex is probably pretty busy working the last day before
qemus hard freeze for 1.4.

Christian


  reply	other threads:[~2013-01-29 20:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-25 14:34 [PATCH 0/3] s390/kvm fixes Christian Borntraeger
2013-01-25 14:34 ` [PATCH 1/3] s390/kvm: Fix store status for ACRS/FPRS Christian Borntraeger
2013-01-25 14:34 ` [PATCH 2/3] s390/virtio-ccw: Fix setup_vq error handling Christian Borntraeger
2013-01-25 14:35   ` Christian Borntraeger
2013-01-25 14:34 ` [PATCH 3/3] s390/kvm: Fix instruction decoding Christian Borntraeger
2013-01-29 13:12 ` [PATCH 0/3] s390/kvm fixes Gleb Natapov
2013-01-29 20:41   ` Christian Borntraeger [this message]
2013-01-29 20:46     ` Gleb Natapov
2013-01-29 21:03       ` Gleb Natapov
2013-01-30  8:51         ` Christian Borntraeger
2013-01-30 10:30           ` Gleb Natapov
2013-01-30 10:36 ` Gleb Natapov

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=510833F1.2000200@de.ibm.com \
    --to=borntraeger@de.ibm.com \
    --cc=agraf@suse.de \
    --cc=cornelia.huck@de.ibm.com \
    --cc=gleb@redhat.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=jfrei@linux.vnet.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=mtosatti@redhat.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