linux-kernel - linux-next: manual merge of the reset tree with the kspp-gustavo 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: <20200819102819.63c9aa50@canb.auug.org.au>
Date:   Wed, 19 Aug 2020 10:28:19 +1000
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Philipp Zabel <p.zabel@...gutronix.de>,
        "Gustavo A. R. Silva" <gustavo@...eddedor.com>
Cc:     Linux Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Peng Fan <peng.fan@....com>
Subject: linux-next: manual merge of the reset tree with the kspp-gustavo
 tree

Hi all,

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

  drivers/reset/reset-imx7.c

between commit:

  58e813cceabd ("treewide: Use fallthrough pseudo-keyword")

from the kspp-gustavo tree and commit:

  2983e2385ff6 ("reset: imx7: add the cm4 reset for i.MX8MQ")

from the reset 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/reset/reset-imx7.c
index e8aa8691deb2,b60534a1e0ef..000000000000
--- a/drivers/reset/reset-imx7.c
+++ b/drivers/reset/reset-imx7.c
@@@ -232,12 -235,13 +235,13 @@@ static int imx8mq_reset_set(struct rese
  		break;
  
  	case IMX8MQ_RESET_PCIE_CTRL_APPS_EN:
 -	case IMX8MQ_RESET_PCIE2_CTRL_APPS_EN:	/* fallthrough */
 -	case IMX8MQ_RESET_MIPI_DSI_PCLK_RESET_N:	/* fallthrough */
 -	case IMX8MQ_RESET_MIPI_DSI_ESC_RESET_N:	/* fallthrough */
 -	case IMX8MQ_RESET_MIPI_DSI_DPI_RESET_N:	/* fallthrough */
 -	case IMX8MQ_RESET_MIPI_DSI_RESET_N:	/* fallthrough */
 -	case IMX8MQ_RESET_MIPI_DSI_RESET_BYTE_N:	/* fallthrough */
 +	case IMX8MQ_RESET_PCIE2_CTRL_APPS_EN:
 +	case IMX8MQ_RESET_MIPI_DSI_PCLK_RESET_N:
 +	case IMX8MQ_RESET_MIPI_DSI_ESC_RESET_N:
 +	case IMX8MQ_RESET_MIPI_DSI_DPI_RESET_N:
 +	case IMX8MQ_RESET_MIPI_DSI_RESET_N:
 +	case IMX8MQ_RESET_MIPI_DSI_RESET_BYTE_N:
+ 	case IMX8MQ_RESET_M4_ENABLE:
  		value = assert ? 0 : bit;
  		break;
  	}

Content of type "application/pgp-signature" skipped