[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20191025125436.6c85dbfe@canb.auug.org.au>
Date: Fri, 25 Oct 2019 12:54:36 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Paul Mackerras <paulus@...abs.org>,
Christoffer Dall <cdall@...columbia.edu>,
Marc Zyngier <marc.zyngier@....com>
Cc: Linux Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Fabiano Rosas <farosas@...ux.ibm.com>,
Paolo Bonzini <pbonzini@...hat.com>,
Radim Krčmář <rkrcmar@...hat.com>,
KVM <kvm@...r.kernel.org>
Subject: linux-next: manual merge of the kvm-ppc tree with the kvm-arm tree
Hi all,
Today's linux-next merge of the kvm-ppc tree got a conflict in:
include/uapi/linux/kvm.h
between commits:
c726200dd106 ("KVM: arm/arm64: Allow reporting non-ISV data aborts to userspace")
da345174ceca ("KVM: arm/arm64: Allow user injection of external data aborts")
from the kvm-arm tree and commit:
1a9167a214f5 ("KVM: PPC: Report single stepping capability")
from the kvm-ppc 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 fb47c0fad6a6,ce8cfcc51aec..000000000000
--- a/include/uapi/linux/kvm.h
+++ b/include/uapi/linux/kvm.h
@@@ -1006,8 -1000,7 +1006,9 @@@ struct kvm_ppc_resize_hpt
#define KVM_CAP_PMU_EVENT_FILTER 173
#define KVM_CAP_ARM_IRQ_LINE_LAYOUT_2 174
#define KVM_CAP_HYPERV_DIRECT_TLBFLUSH 175
-#define KVM_CAP_PPC_GUEST_DEBUG_SSTEP 176
+#define KVM_CAP_ARM_NISV_TO_USER 176
+#define KVM_CAP_ARM_INJECT_EXT_DABT 177
++#define KVM_CAP_PPC_GUEST_DEBUG_SSTEP 178
#ifdef KVM_CAP_IRQ_ROUTING
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists