[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220520154055.7f964b76@canb.auug.org.au>
Date: Fri, 20 May 2022 15:40:55 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Luis Chamberlain <mcgrof@...nel.org>,
Michael Ellerman <mpe@...erman.id.au>
Cc: PowerPC <linuxppc-dev@...ts.ozlabs.org>,
Christophe Leroy <christophe.leroy@...roup.eu>,
Daniel Axtens <dja@...ens.net>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Paul Mackerras <paulus@...abs.org>
Subject: linux-next: manual merge of the modules tree with the powerpc tree
Hi all,
Today's linux-next merge of the modules tree got a conflict in:
arch/powerpc/Kconfig
between commit:
b91d4eea5bff ("powerpc: Book3S 64-bit outline-only KASAN support")
from the powerpc tree and commit:
eeaec7801c42 ("powerpc: Select ARCH_WANTS_MODULES_DATA_IN_VMALLOC on book3s/32 and 8xx")
from the modules 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/powerpc/Kconfig
index dddace39d005,0b7bcfa63d0d..000000000000
--- a/arch/powerpc/Kconfig
+++ b/arch/powerpc/Kconfig
@@@ -158,7 -157,7 +158,8 @@@ config PP
select ARCH_WANT_IPC_PARSE_VERSION
select ARCH_WANT_IRQS_OFF_ACTIVATE_MM
select ARCH_WANT_LD_ORPHAN_WARN
+ select ARCH_WANTS_MODULES_DATA_IN_VMALLOC if PPC_BOOK3S_32 || PPC_8xx
+ select ARCH_WANTS_NO_INSTR
select ARCH_WEAK_RELEASE_ACQUIRE
select BINFMT_ELF
select BUILDTIME_TABLE_SORT
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists