linux-next: manual merge of the nds32 tree with the kbuild tree

linux-next: manual merge of the nds32 tree with the kbuild tree

[Stephen Rothwell]

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

Hi all,

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

  arch/nds32/Kbuild

between commit:

  8212f8986d31 ("kbuild: use more subdir- for visiting subdirectories while cleaning")

from the kbuild tree and commit:

  37160f01e8ea ("nds32: move core-y in arch/nds32/Makefile to arch/nds32/Kbuild")

from the nds32 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/nds32/Kbuild
index 4e39f7abdeb6,565b9bc3c9db..000000000000
--- a/arch/nds32/Kbuild
+++ b/arch/nds32/Kbuild
@@@ -1,4 -1,4 +1,7 @@@
  # SPDX-License-Identifier: GPL-2.0-only
+ obj-y			+= kernel/ mm/
+ obj-$(CONFIG_FPU)	+= math-emu/
+ obj-y			+= boot/dts/
 +
 +# for cleaning
 +subdir- += boot

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

Re: linux-next: manual merge of the nds32 tree with the kbuild tree

[Stephen Rothwell]

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

Hi all,

On Mon, 25 Oct 2021 09:38:13 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Today's linux-next merge of the nds32 tree got a conflict in:
> 
>   arch/nds32/Kbuild
> 
> between commit:
> 
>   8212f8986d31 ("kbuild: use more subdir- for visiting subdirectories while cleaning")
> 
> from the kbuild tree and commit:
> 
>   37160f01e8ea ("nds32: move core-y in arch/nds32/Makefile to arch/nds32/Kbuild")
> 
> from the nds32 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.
> 
> 
> diff --cc arch/nds32/Kbuild
> index 4e39f7abdeb6,565b9bc3c9db..000000000000
> --- a/arch/nds32/Kbuild
> +++ b/arch/nds32/Kbuild
> @@@ -1,4 -1,4 +1,7 @@@
>   # SPDX-License-Identifier: GPL-2.0-only
> + obj-y			+= kernel/ mm/
> + obj-$(CONFIG_FPU)	+= math-emu/
> + obj-y			+= boot/dts/
>  +
>  +# for cleaning
>  +subdir- += boot

I am still getting this conflict (and another on arch/nds32/Kconfig),
and so am wondering when the nds32 tree will be submitted to Linus for
merging?  It has not been updated since last September.

-- 
Cheers,
Stephen Rothwell

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

linux-next: manual merge of the nds32 tree with the kbuild tree

[broonie]

Hi all,

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

  arch/nds32/Kbuild

between commit:

  8212f8986d311 ("kbuild: use more subdir- for visiting subdirectories while cleaning")

from the kbuild tree and commit:

  37160f01e8ea6 ("nds32: move core-y in arch/nds32/Makefile to arch/nds32/Kbuild")

from the nds32 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.

diff --cc arch/nds32/Kbuild
index ac127371afa47,565b9bc3c9db4..0000000000000
--- a/arch/nds32/Kbuild
+++ b/arch/nds32/Kbuild
diff --cc arch/nds32/Kconfig
index 013249430fa3d,a20b42d4bdb6e..0000000000000
--- a/arch/nds32/Kconfig
+++ b/arch/nds32/Kconfig
@@@ -61,6 -63,12 +60,9 @@@ config GENERIC_LOCKBREA
  	def_bool y
  	depends on PREEMPTION
  
+ config LOCKDEP_SUPPORT
+ 	def_bool y
+ 
 -config TRACE_IRQFLAGS_SUPPORT
 -	def_bool y
 -
  config STACKTRACE_SUPPORT
  	def_bool y