linux-kernel - linux-next: manual merge of the mmc tree with the arm-soc, crypto trees

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>] [day] [month] [year] [list]

Message-ID: <20230215111623.06d9aa24@canb.auug.org.au>
Date:   Wed, 15 Feb 2023 11:16:23 +1100
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Ulf Hansson <ulf.hansson@...aro.org>,
        Olof Johansson <olof@...om.net>, Arnd Bergmann <arnd@...db.de>,
        Herbert Xu <herbert@...dor.apana.org.au>
Cc:     Linux Crypto List <linux-crypto@...r.kernel.org>,
        ARM <linux-arm-kernel@...ts.infradead.org>,
        Conor Dooley <conor.dooley@...rochip.com>,
        Jenny Zhang <jenny.zhang@...rfivetech.com>,
        Jia Jie Ho <jiajie.ho@...rfivetech.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        Walker Chen <walker.chen@...rfivetech.com>,
        William Qiu <william.qiu@...rfivetech.com>
Subject: linux-next: manual merge of the mmc tree with the arm-soc, crypto
 trees

Hi all,

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

  MAINTAINERS

between commits:

  08b9a94e8654 ("soc: starfive: Add StarFive JH71XX pmu driver")
  c388f458bc34 ("hwrng: starfive - Add TRNG driver for StarFive SoC")

from the arm-soc, crypto trees and commit:

  bfde6b3869f5 ("mmc: starfive: Add sdio/emmc driver support")

from the mmc 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 MAINTAINERS
index 9262a1d7203d,71355c68a237..000000000000
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@@ -19840,25 -19926,12 +19840,31 @@@ F:	Documentation/devicetree/bindings/re
  F:	drivers/reset/reset-starfive-jh7100.c
  F:	include/dt-bindings/reset/starfive-jh7100.h
  
+ STARFIVE JH7110 MMC/SD/SDIO DRIVER
+ M:	William Qiu <william.qiu@...rfivetech.com>
+ S:	Maintained
+ F:	Documentation/devicetree/bindings/mmc/starfive*
+ F:	drivers/mmc/dw_mmc-starfive.c
+ 
 +STARFIVE JH71XX PMU CONTROLLER DRIVER
 +M:	Walker Chen <walker.chen@...rfivetech.com>
 +S:	Supported
 +F:	Documentation/devicetree/bindings/power/starfive*
 +F:	drivers/soc/starfive/jh71xx_pmu.c
 +F:	include/dt-bindings/power/starfive,jh7110-pmu.h
 +
 +STARFIVE SOC DRIVERS
 +M:	Conor Dooley <conor@...nel.org>
 +S:	Maintained
 +T:	git https://git.kernel.org/pub/scm/linux/kernel/git/conor/linux.git/
 +F:	drivers/soc/starfive/
 +
 +STARFIVE TRNG DRIVER
 +M:	Jia Jie Ho <jiajie.ho@...rfivetech.com>
 +S:	Supported
 +F:	Documentation/devicetree/bindings/rng/starfive*
 +F:	drivers/char/hw_random/jh7110-trng.c
 +
  STATIC BRANCH/CALL
  M:	Peter Zijlstra <peterz@...radead.org>
  M:	Josh Poimboeuf <jpoimboe@...nel.org>

Content of type "application/pgp-signature" skipped