All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Radim Krčmář" <rkrcmar@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>, 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>,
	Marc Zyngier <marc.zyngier@arm.com>,
	Christoffer Dall <christoffer.dall@linaro.org>
Subject: Re: PREVIEW: [GIT PULL 0/2] KVM: s390: Feature and fix for kvm/next (4.8) part 4
Date: Thu, 21 Jul 2016 15:07:18 +0200	[thread overview]
Message-ID: <20160721130717.GA2317@potion> (raw)
In-Reply-To: <1469018400-8397-1-git-send-email-borntraeger@de.ibm.com>

2016-07-20 14:39+0200, Christian Borntraeger:
> Paolo, Radim,
> 
> hopefully the last update for s390 for 4.8.
> Please note the CAP number conflicts with kvmarm, when merging the one
> or the other first. You might also need to adopt the number in
> Documentation/virtual/kvm/api.txt in case arm has something in here as well.

Merged, thanks.  Capability 130 is KVM_CAP_S390_USER_INSTR0.

      parent reply	other threads:[~2016-07-21 13:07 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
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ář [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=20160721130717.GA2317@potion \
    --to=rkrcmar@redhat.com \
    --cc=borntraeger@de.ibm.com \
    --cc=christoffer.dall@linaro.org \
    --cc=cornelia.huck@de.ibm.com \
    --cc=dahi@linux.vnet.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=marc.zyngier@arm.com \
    --cc=pbonzini@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.