From: Marc Zyngier <marc.zyngier@arm.com>
To: "Christian Borntraeger" <borntraeger@de.ibm.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Radim Krčmář" <rkrcmar@redhat.com>
Cc: KVM <kvm@vger.kernel.org>,
Cornelia Huck <cornelia.huck@de.ibm.com>,
linux-s390 <linux-s390@vger.kernel.org>,
David Hildenbrand <dahi@linux.vnet.ibm.com>,
cdall@cs.columbia.edu
Subject: Re: [GIT PULL 1/2] KVM: s390: allow user space to handle instr 0x0000
Date: Wed, 20 Jul 2016 18:47:22 +0100 [thread overview]
Message-ID: <578FB92A.5030806@arm.com> (raw)
In-Reply-To: <578F8C45.6060505@de.ibm.com>
On 20/07/16 15:35, Christian Borntraeger wrote:
> Marc, Christoffer,
> FYI/FYA
> the CAP number will conflict with your kvmarm changes.
> I assume Paolo/Radim will resolve this when merging.
Yea, that's usually the case.
> Seems that you have no hit in api.txt, correct?
There is a small update for the KVM_CAP_SIGNAL_MSI API, but we don't
seem to step on each other's toes over there.
Thanks for the heads up!
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2016-07-20 17:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-20 12:39 PREVIEW: [GIT PULL 0/2] KVM: s390: Feature and fix for kvm/next (4.8) part 4 Christian Borntraeger
2016-07-20 12:39 ` [GIT PULL 1/2] KVM: s390: allow user space to handle instr 0x0000 Christian Borntraeger
2016-07-20 14:35 ` Christian Borntraeger
2016-07-20 14:43 ` Paolo Bonzini
2016-07-20 17:47 ` Marc Zyngier [this message]
2016-07-20 12:40 ` [GIT PULL 2/2] KVM: s390: let ptff intercepts result in cc=3 Christian Borntraeger
2016-07-20 12:41 ` PREVIEW: [GIT PULL 0/2] KVM: s390: Feature and fix for kvm/next (4.8) part 4 Christian Borntraeger
2016-07-21 13:07 ` Radim Krčmář
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=578FB92A.5030806@arm.com \
--to=marc.zyngier@arm.com \
--cc=borntraeger@de.ibm.com \
--cc=cdall@cs.columbia.edu \
--cc=cornelia.huck@de.ibm.com \
--cc=dahi@linux.vnet.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.