linux-next: manual merge of the nand tree with the mtd-fixes tree

Stephen Rothwell posted 1 patch 1 week, 2 days ago
linux-next: manual merge of the nand tree with the mtd-fixes tree
Posted by Stephen Rothwell 1 week, 2 days ago
Hi all,

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

  drivers/mtd/nand/onenand/Kconfig

between commit:

  c717b9b7d6de ("mtd: onenand: omap2: add dependency on GPMC")

from the mtd-fixes tree and commit:

  b46ff0780f17 ("mtd: onenand: omap2: Drop obsolete dependency on COMPILE_TEST")

from the nand 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 drivers/mtd/nand/onenand/Kconfig
index c94bf483541e,5c240533cea4..000000000000
--- a/drivers/mtd/nand/onenand/Kconfig
+++ b/drivers/mtd/nand/onenand/Kconfig
@@@ -25,8 -25,7 +25,8 @@@ config MTD_ONENAND_GENERI
  config MTD_ONENAND_OMAP2
  	tristate "OneNAND on OMAP2/OMAP3 support"
  	depends on ARCH_OMAP2 || ARCH_OMAP3 || (COMPILE_TEST && ARM)
- 	depends on OF || COMPILE_TEST
+ 	depends on OF
 +	depends on OMAP_GPMC
  	help
  	  Support for a OneNAND flash device connected to an OMAP2/OMAP3 SoC
  	  via the GPMC memory controller.
Re: linux-next: manual merge of the nand tree with the mtd-fixes tree
Posted by Miquel Raynal 1 week, 2 days ago
Hi Jean,

sfr@canb.auug.org.au wrote on Fri, 25 Nov 2022 09:46:34 +1100:

> Hi all,
> 
> Today's linux-next merge of the nand tree got a conflict in:
> 
>   drivers/mtd/nand/onenand/Kconfig
> 
> between commit:
> 
>   c717b9b7d6de ("mtd: onenand: omap2: add dependency on GPMC")
> 
> from the mtd-fixes tree and commit:
> 
>   b46ff0780f17 ("mtd: onenand: omap2: Drop obsolete dependency on COMPILE_TEST")

As this commit is not super urgent and because I want to make the merge
process as smooth as possible, I'll drop it from my branches. Please
rebase and resend when -rc1 is out and I'll apply right away.

Thanks Stephen for the report.

Cheers,
Miquèl

> 
> from the nand 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.
> 
Re: linux-next: manual merge of the nand tree with the mtd-fixes tree
Posted by Jean Delvare 1 week, 2 days ago
On Fri, 25 Nov 2022 10:05:04 +0100, Miquel Raynal wrote:
> sfr@canb.auug.org.au wrote on Fri, 25 Nov 2022 09:46:34 +1100:
> > Today's linux-next merge of the nand tree got a conflict in:
> > 
> >   drivers/mtd/nand/onenand/Kconfig
> > 
> > between commit:
> > 
> >   c717b9b7d6de ("mtd: onenand: omap2: add dependency on GPMC")
> > 
> > from the mtd-fixes tree and commit:
> > 
> >   b46ff0780f17 ("mtd: onenand: omap2: Drop obsolete dependency on COMPILE_TEST")  
> 
> As this commit is not super urgent and because I want to make the merge
> process as smooth as possible, I'll drop it from my branches. Please
> rebase and resend when -rc1 is out and I'll apply right away.

Noted, no problem.

-- 
Jean Delvare
SUSE L3 Support