From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Christian Borntraeger <borntraeger@de.ibm.com>,
Cornelia Huck <cornelia.huck@de.ibm.com>,
Christoffer Dall <cdall@cs.columbia.edu>,
Marc Zyngier <marc.zyngier@arm.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
David Hildenbrand <dahi@linux.vnet.ibm.com>,
Andre Przywara <andre.przywara@arm.com>
Subject: linux-next: manual merge of the kvms390 tree with the kvm-arm tree
Date: Wed, 20 Jul 2016 15:34:37 +1000 [thread overview]
Message-ID: <20160720153437.7cddb065@canb.auug.org.au> (raw)
Hi all,
Today's linux-next merge of the kvms390 tree got a conflict in:
include/uapi/linux/kvm.h
between commit:
2b8ddd9337ee ("KVM: Extend struct kvm_msi to hold a 32-bit device ID")
from the kvm-arm tree and commit:
6502a34cfd66 ("KVM: s390: allow user space to handle instr 0x0000")
from the kvms390 tree.
I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging. You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.
--
Cheers,
Stephen Rothwell
diff --cc include/uapi/linux/kvm.h
index 84d9e5f8ab4b,70941f4ab6d8..000000000000
--- a/include/uapi/linux/kvm.h
+++ b/include/uapi/linux/kvm.h
@@@ -867,7 -867,7 +867,8 @@@ struct kvm_ppc_smmu_info
#define KVM_CAP_VCPU_ATTRIBUTES 127
#define KVM_CAP_MAX_VCPU_ID 128
#define KVM_CAP_X2APIC_API 129
-#define KVM_CAP_S390_USER_INSTR0 130
+#define KVM_CAP_MSI_DEVID 130
++#define KVM_CAP_S390_USER_INSTR0 131
#ifdef KVM_CAP_IRQ_ROUTING
next reply other threads:[~2016-07-20 5:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-20 5:34 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-06-09 4:28 linux-next: manual merge of the kvms390 tree with the kvm-arm tree Stephen Rothwell
2017-06-28 6:02 ` Stephen Rothwell
2017-06-28 7:10 ` Christian Borntraeger
2018-07-31 4:23 Stephen Rothwell
2018-08-02 1:19 ` Stephen Rothwell
2018-08-02 13:18 ` Paolo Bonzini
2022-11-16 3:03 Stephen Rothwell
2025-11-21 3:17 Stephen Rothwell
2025-11-21 3:20 Stephen Rothwell
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=20160720153437.7cddb065@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=andre.przywara@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=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=marc.zyngier@arm.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