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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20221125094634.665b079c@canb.auug.org.au>
Date:   Fri, 25 Nov 2022 09:46:34 +1100
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Miquel Raynal <miquel.raynal@...tlin.com>,
        Boris Brezillon <boris.brezillon@...labora.com>
Cc:     Jean Delvare <jdelvare@...e.de>,
        Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: linux-next: manual merge of the nand tree with the mtd-fixes tree

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.

Content of type "application/pgp-signature" skipped