All of lore.kernel.org
 help / color / mirror / Atom feed
* linux-next: manual merge of the at91 tree with Linus' tree
@ 2021-10-21 21:56 Stephen Rothwell
  2021-10-22  9:38 ` Nicolas Ferre
  0 siblings, 1 reply; 2+ messages in thread
From: Stephen Rothwell @ 2021-10-21 21:56 UTC (permalink / raw)
  To: Nicolas Ferre, Alexandre Belloni, Ludovic Desroches
  Cc: Claudiu Beznea, Linux Kernel Mailing List,
	Linux Next Mailing List, Nicolas Ferre

[-- Attachment #1: Type: text/plain, Size: 1659 bytes --]

Hi all,

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

  arch/arm/boot/dts/sama7g5.dtsi

between commit:

  6f3466228451 ("ARM: dts: at91: sama7g5: add chipid")

from Linus' tree and commit:

  9430ff34385e ("ARM: dts: at91: sama7g5: add tcb nodes")

from the at91 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 arch/arm/boot/dts/sama7g5.dtsi
index f98977f3980d,c75c7d7c2842..000000000000
--- a/arch/arm/boot/dts/sama7g5.dtsi
+++ b/arch/arm/boot/dts/sama7g5.dtsi
@@@ -159,11 -144,16 +166,21 @@@
  			clocks = <&clk32k 0>;
  		};
  
 +		chipid@e0020000 {
 +			compatible = "microchip,sama7g5-chipid";
 +			reg = <0xe0020000 0x8>;
 +		};
 +
+ 		tcb1: timer@e0800000 {
+ 			compatible = "atmel,sama5d2-tcb", "simple-mfd", "syscon";
+ 			#address-cells = <1>;
+ 			#size-cells = <0>;
+ 			reg = <0xe0800000 0x100>;
+ 			interrupts = <GIC_SPI 91 IRQ_TYPE_LEVEL_HIGH>, <GIC_SPI 92 IRQ_TYPE_LEVEL_HIGH>, <GIC_SPI 93 IRQ_TYPE_LEVEL_HIGH>;
+ 			clocks = <&pmc PMC_TYPE_PERIPHERAL 91>, <&pmc PMC_TYPE_PERIPHERAL 92>, <&pmc PMC_TYPE_PERIPHERAL 93>, <&clk32k 1>;
+ 			clock-names = "t0_clk", "t1_clk", "t2_clk", "slow_clk";
+ 		};
+ 
  		adc: adc@e1000000 {
  			compatible = "microchip,sama7g5-adc";
  			reg = <0xe1000000 0x200>;

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: linux-next: manual merge of the at91 tree with Linus' tree
  2021-10-21 21:56 linux-next: manual merge of the at91 tree with Linus' tree Stephen Rothwell
@ 2021-10-22  9:38 ` Nicolas Ferre
  0 siblings, 0 replies; 2+ messages in thread
From: Nicolas Ferre @ 2021-10-22  9:38 UTC (permalink / raw)
  To: Stephen Rothwell, Nicolas Ferre, Alexandre Belloni, Ludovic Desroches
  Cc: Claudiu Beznea, Linux Kernel Mailing List, Linux Next Mailing List

On 21/10/2021 at 23:56, Stephen Rothwell wrote:
> Hi all,
> 
> Today's linux-next merge of the at91 tree got a conflict in:
> 
>    arch/arm/boot/dts/sama7g5.dtsi
> 
> between commit:
> 
>    6f3466228451 ("ARM: dts: at91: sama7g5: add chipid")
> 
> from Linus' tree and commit:
> 
>    9430ff34385e ("ARM: dts: at91: sama7g5: add tcb nodes")
> 
> from the at91 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.

Stephen,

Yes, carry this fix please.
It's handled in arm-soc tree by Arnd and Olof: should not be a problem 
upstream.

Thanks, best regards,
   Nicolas

-- 
Nicolas Ferre

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2021-10-22  9:38 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-10-21 21:56 linux-next: manual merge of the at91 tree with Linus' tree Stephen Rothwell
2021-10-22  9:38 ` Nicolas Ferre

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.