From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Christian Borntraeger <borntraeger@de•ibm.com>,
Cornelia Huck <cornelia.huck@de•ibm.com>,
Paul Mackerras <paulus@ozlabs•org>
Cc: Linux-Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Aravinda Prasad <aravinda@linux•vnet.ibm.com>,
Claudio Imbrenda <imbrenda@linux•vnet.ibm.com>,
Marcelo Tosatti <mtosatti@redhat•com>,
Gleb Natapov <gleb@kernel•org>, KVM <kvm@vger•kernel.org>
Subject: linux-next: manual merge of the kvms390 tree with the kvm-ppc tree
Date: Thu, 29 Jun 2017 13:37:52 +1000 [thread overview]
Message-ID: <20170629133752.294bef54@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 commits:
134764ed6e12 ("KVM: PPC: Book3S HV: Add new capability to control MCE behaviour")
2ed4f9dd19c0 ("KVM: PPC: Book3S HV: Add capability to report possible virtual SMT modes")
from the kvm-ppc tree and commit:
4036e3874a1c ("KVM: s390: ioctls to get and set guest storage attributes")
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 36ea74aa3422,2b8dc1ca18d4..000000000000
--- a/include/uapi/linux/kvm.h
+++ b/include/uapi/linux/kvm.h
@@@ -895,8 -924,7 +924,9 @@@ struct kvm_ppc_resize_hpt
#define KVM_CAP_SPAPR_TCE_VFIO 142
#define KVM_CAP_X86_GUEST_MWAIT 143
#define KVM_CAP_ARM_USER_IRQ 144
-#define KVM_CAP_S390_CMMA_MIGRATION 145
+#define KVM_CAP_PPC_FWNMI 145
+#define KVM_CAP_PPC_SMT_POSSIBLE 146
++#define KVM_CAP_S390_CMMA_MIGRATION 147
#ifdef KVM_CAP_IRQ_ROUTING
reply other threads:[~2017-06-29 3:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20170629133752.294bef54@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=aravinda@linux$(echo .)vnet.ibm.com \
--cc=borntraeger@de$(echo .)ibm.com \
--cc=cornelia.huck@de$(echo .)ibm.com \
--cc=gleb@kernel$(echo .)org \
--cc=imbrenda@linux$(echo .)vnet.ibm.com \
--cc=kvm@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mtosatti@redhat$(echo .)com \
--cc=paulus@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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