linux-kernel - linux-next: manual merge of the keystone tree with the arm-soc 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>] [day] [month] [year] [list]

Message-ID: <20171030120530.rmyan374grqenqyj@sirena.co.uk>
Date:   Mon, 30 Oct 2017 12:05:30 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Santosh Shilimkar <santosh.shilimkar@...com>, arnd@...db.de,
        rob.herring@...aro.org
Cc:     linux-arm-kernel@...ts.infradead.org,
        Linux-Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: linux-next: manual merge of the keystone tree with the arm-soc tree

Hi Santosh,

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

  arch/arm/boot/dts/keystone-k2g.dtsi

between commit:

  8dccafaa281aa1d24 ("arm: dts: fix unit-address leading 0s")

from the arm-soc tree and various commits from the keystone 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/arm/boot/dts/keystone-k2g.dtsi
index a1ae69d712f7,6f3521d18125..000000000000
--- a/arch/arm/boot/dts/keystone-k2g.dtsi
+++ b/arch/arm/boot/dts/keystone-k2g.dtsi
@@@ -133,7 -136,40 +136,40 @@@
  			clocks = <&k2g_clks 0x0009 1>;
  		};
  
+ 		i2c0: i2c@...0000 {
+ 			compatible = "ti,keystone-i2c";
+ 			reg = <0x02530000 0x400>;
+ 			clocks = <&k2g_clks 0x003a 0>;
+ 			power-domains = <&k2g_pds 0x003a>;
+ 			interrupts = <GIC_SPI 88 IRQ_TYPE_EDGE_RISING>;
+ 			#address-cells = <1>;
+ 			#size-cells = <0>;
+ 			status = "disabled";
+ 		};
+ 
+ 		i2c1: i2c@...0400 {
+ 			compatible = "ti,keystone-i2c";
+ 			reg = <0x02530400 0x400>;
+ 			clocks = <&k2g_clks 0x003b 0>;
+ 			power-domains = <&k2g_pds 0x003b>;
+ 			interrupts = <GIC_SPI 89 IRQ_TYPE_EDGE_RISING>;
+ 			#address-cells = <1>;
+ 			#size-cells = <0>;
+ 			status = "disabled";
+ 		};
+ 
+ 		i2c2: i2c@...0800 {
+ 			compatible = "ti,keystone-i2c";
+ 			reg = <0x02530800 0x400>;
+ 			clocks = <&k2g_clks 0x003c 0>;
+ 			power-domains = <&k2g_pds 0x003c>;
+ 			interrupts = <GIC_SPI 90 IRQ_TYPE_EDGE_RISING>;
+ 			#address-cells = <1>;
+ 			#size-cells = <0>;
+ 			status = "disabled";
+ 		};
+ 
 -		kirq0: keystone_irq@...202a0 {
 +		kirq0: keystone_irq@...02a0 {
  			compatible = "ti,keystone-irq";
  			interrupts = <GIC_SPI 1 IRQ_TYPE_EDGE_RISING>;
  			interrupt-controller;

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)