[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220526130228.332e59a7@canb.auug.org.au>
Date: Thu, 26 May 2022 13:02:28 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>,
Peter Zijlstra <peterz@...radead.org>,
Palmer Dabbelt <palmer@...belt.com>,
Paul Walmsley <paul@...an.com>
Cc: Guo Ren <guoren@...nel.org>, Guo Ren <guoren@...ux.alibaba.com>,
Ingo Molnar <mingo@...nel.org>,
Juerg Haefliger <juerg.haefliger@...onical.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Palmer Dabbelt <palmer@...osinc.com>
Subject: linux-next: manual merge of the tip tree with the risc-v tree
Hi all,
Today's linux-next merge of the tip tree got a conflict in:
arch/x86/Kconfig
between commit:
0cbed0ee1dbc ("arch: Add SYSVIPC_COMPAT for all architectures")
from the risc-v tree and commit:
758cd94a0e16 ("x86/Kconfig: Fix indentation and add endif comments to arch/x86/Kconfig")
from the tip 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 arch/x86/Kconfig
index 98eaa8870f28,4d610ae216ce..000000000000
--- a/arch/x86/Kconfig
+++ b/arch/x86/Kconfig
@@@ -2869,7 -2861,11 +2867,7 @@@ config COMPA
if COMPAT
config COMPAT_FOR_U64_ALIGNMENT
def_bool y
- endif
-
-config SYSVIPC_COMPAT
- def_bool y
- depends on SYSVIPC
+ endif # COMPAT
endmenu
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists