[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20251120155205.0d145852@canb.auug.org.au>
Date: Thu, 20 Nov 2025 15:52:05 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Sean Christopherson <seanjc@...gle.com>, Thomas Gleixner
<tglx@...utronix.de>, Ingo Molnar <mingo@...nel.org>, "H. Peter Anvin"
<hpa@...or.com>, Peter Zijlstra <peterz@...radead.org>
Cc: Dave Hansen <dave.hansen@...ux.intel.com>, Elena Reshetova
<elena.reshetova@...el.com>, Linux Kernel Mailing List
<linux-kernel@...r.kernel.org>, Linux Next Mailing List
<linux-next@...r.kernel.org>, Naveen N Rao <naveen@...nel.org>
Subject: linux-next: manual merge of the kvm-x86 tree with the tip tree
Hi all,
Today's linux-next merge of the kvm-x86 tree got a conflict in:
arch/x86/include/asm/cpufeatures.h
between commit:
6ffdb49101f0 ("x86/cpufeatures: Add X86_FEATURE_SGX_EUPDATESVN feature flag")
from the tip tree and commits:
5d0316e25def ("x86/cpufeatures: Add X86_FEATURE_X2AVIC_EXT")
f6106d41ec84 ("x86/bugs: Use an x86 feature to track the MMIO Stale Data mitigation")
9c6bbdaab7e6 ("Merge branch 'svm'")
from the kvm-x86 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
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists