linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* linux-next: manual merge of the mips tree with the kbuild tree
@ 2018-11-25 23:17 Stephen Rothwell
  0 siblings, 0 replies; 8+ messages in thread
From: Stephen Rothwell @ 2018-11-25 23:17 UTC (permalink / raw)
  To: Ralf Baechle, James Hogan, Masahiro Yamada
  Cc: Linux Next Mailing List, Linux Kernel Mailing List,
	Christoph Hellwig, Maksym Kokhan, Paul Burton, Andrii Bordunov

[-- Attachment #1: Type: text/plain, Size: 1592 bytes --]

Hi all,

Today's linux-next merge of the mips tree got a conflict in:

  arch/mips/Kconfig

between commit:

  eb01d42a7778 ("PCI: consolidate PCI config entry in drivers/pci")

from the kbuild tree and commit:

  47bf2b031754 ("mips: sort list of configs for Malta")

from the mips 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/mips/Kconfig
index f4df8007fddb,e49b5a0c8585..000000000000
--- a/arch/mips/Kconfig
+++ b/arch/mips/Kconfig
@@@ -495,22 -498,23 +499,23 @@@ config MIPS_MALT
  	select BOOT_RAW
  	select BUILTIN_DTB
  	select CEVT_R4K
- 	select CSRC_R4K
  	select CLKSRC_MIPS_GIC
  	select COMMON_CLK
+ 	select CSRC_R4K
  	select DMA_MAYBE_COHERENT
  	select GENERIC_ISA_DMA
- 	select HAVE_PCSPKR_PLATFORM
- 	select IRQ_MIPS_CPU
- 	select MIPS_GIC
 +	select HAVE_PCI
+ 	select HAVE_PCSPKR_PLATFORM
 -	select HW_HAS_PCI
  	select I8253
  	select I8259
+ 	select IRQ_MIPS_CPU
+ 	select LIBFDT
  	select MIPS_BONITO64
  	select MIPS_CPU_SCACHE
+ 	select MIPS_GIC
  	select MIPS_L1_CACHE_SHIFT_6
- 	select PCI_GT64XXX_PCI0
  	select MIPS_MSC
+ 	select PCI_GT64XXX_PCI0
  	select SMP_UP if SMP
  	select SWAP_IO_SPACE
  	select SYS_HAS_CPU_MIPS32_R1

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 8+ messages in thread
* linux-next: manual merge of the mips tree with the kbuild tree
@ 2019-08-25 23:17 Stephen Rothwell
  0 siblings, 0 replies; 8+ messages in thread
From: Stephen Rothwell @ 2019-08-25 23:17 UTC (permalink / raw)
  To: Ralf Baechle, James Hogan, Masahiro Yamada
  Cc: Linux Next Mailing List, Linux Kernel Mailing List,
	Daniel Silsby, Paul Burton, Paul Cercueil

[-- Attachment #1: Type: text/plain, Size: 1292 bytes --]

Hi all,

Today's linux-next merge of the mips tree got a conflict in:

  arch/mips/Kconfig

between commit:

  2ff2b7ec65dc ("kbuild: add CONFIG_ASM_MODVERSIONS")

from the kbuild tree and commit:

  45e03e62724f ("MIPS: Decouple CPU_SUPPORTS_HUGEPAGES from 64BIT")

from the mips 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/mips/Kconfig
index 3db919b5c93a,31c7044e34e6..000000000000
--- a/arch/mips/Kconfig
+++ b/arch/mips/Kconfig
@@@ -43,8 -44,7 +44,8 @@@ config MIP
  	select HAVE_ARCH_MMAP_RND_COMPAT_BITS if MMU && COMPAT
  	select HAVE_ARCH_SECCOMP_FILTER
  	select HAVE_ARCH_TRACEHOOK
- 	select HAVE_ARCH_TRANSPARENT_HUGEPAGE if CPU_SUPPORTS_HUGEPAGES && 64BIT
+ 	select HAVE_ARCH_TRANSPARENT_HUGEPAGE if CPU_SUPPORTS_HUGEPAGES
 +	select HAVE_ASM_MODVERSIONS
  	select HAVE_EBPF_JIT if (!CPU_MICROMIPS)
  	select HAVE_CONTEXT_TRACKING
  	select HAVE_COPY_THREAD_TLS

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 8+ messages in thread
* linux-next: manual merge of the mips tree with the kbuild tree
@ 2018-08-02 23:21 Stephen Rothwell
  2018-08-03  6:41 ` Christoph Hellwig
  2018-08-14 23:31 ` Stephen Rothwell
  0 siblings, 2 replies; 8+ messages in thread
From: Stephen Rothwell @ 2018-08-02 23:21 UTC (permalink / raw)
  To: Ralf Baechle, James Hogan, Masahiro Yamada
  Cc: Linux-Next Mailing List, Linux Kernel Mailing List, Paul Burton,
	Christoph Hellwig

[-- Attachment #1: Type: text/plain, Size: 752 bytes --]

Hi all,

Today's linux-next merge of the mips tree got a conflict in:

  arch/mips/Kconfig

between commit:

  1572497cb0e6 ("kconfig: include common Kconfig files from top-level Kconfig")

from the kbuild tree and commit:

  6c359eb1dcdb ("MIPS: Allow auto-dection of ARCH_PFN_OFFSET & PHYS_OFFSET")

from the mips 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

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 8+ messages in thread

end of thread, other threads:[~2019-08-25 23:18 UTC | newest]

Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-11-25 23:17 linux-next: manual merge of the mips tree with the kbuild tree Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2019-08-25 23:17 Stephen Rothwell
2018-08-02 23:21 Stephen Rothwell
2018-08-03  6:41 ` Christoph Hellwig
2018-08-03  6:42   ` Stephen Rothwell
2018-08-03  7:12     ` Christoph Hellwig
2018-08-03  7:51       ` Stephen Rothwell
2018-08-14 23:31 ` Stephen Rothwell

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).