linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* linux-next: manual merge of the mailbox tree with the devicetree tree
@ 2019-11-28  0:41 Stephen Rothwell
  2019-11-28  9:25 ` Arnaud POULIQUEN
  0 siblings, 1 reply; 5+ messages in thread
From: Stephen Rothwell @ 2019-11-28  0:41 UTC (permalink / raw)
  To: Jassi Brar, Rob Herring
  Cc: Linux Next Mailing List, Linux Kernel Mailing List,
	Arnaud Pouliquen, Fabien Dessenne

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

Hi all,

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

  Documentation/devicetree/bindings/mailbox/stm32-ipcc.txt

between commit:

  4360bf724483 ("dt-bindings: mailbox: convert stm32-ipcc to json-schema")

from the devicetree tree and commit:

  9b2cfd3fb09e ("dt-bindings: mailbox: stm32-ipcc: Updates for wakeup management")

from the mailbox tree.

I fixed it up (I just deleted the file - presumably there will need to be
followup fixes to the json file) 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

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

^ permalink raw reply	[flat|nested] 5+ messages in thread
* linux-next: manual merge of the mailbox tree with the devicetree tree
@ 2022-05-23  4:05 Stephen Rothwell
  2022-05-23 14:33 ` Krzysztof Kozlowski
  0 siblings, 1 reply; 5+ messages in thread
From: Stephen Rothwell @ 2022-05-23  4:05 UTC (permalink / raw)
  To: Jassi Brar, Rob Herring
  Cc: David Heidelberg, Krzysztof Kozlowski, Linux Kernel Mailing List,
	Linux Next Mailing List, Rob Herring

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

Hi all,

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

  Documentation/devicetree/bindings/mailbox/qcom-ipcc.yaml

between commit:

  b20eee62ee89 ("dt-bindings: mailbox: qcom-ipcc: add missing properties into example")

from the devicetree tree and commit:

  cd285535b8ee ("dt-bindings: mailbox: qcom-ipcc: simplify the example")

from the mailbox 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 Documentation/devicetree/bindings/mailbox/qcom-ipcc.yaml
index 50f9aa72c670,dfdc72345a2a..000000000000
--- a/Documentation/devicetree/bindings/mailbox/qcom-ipcc.yaml
+++ b/Documentation/devicetree/bindings/mailbox/qcom-ipcc.yaml
@@@ -62,28 -61,14 +62,28 @@@ additionalProperties: fals
  
  examples:
    - |
-         #include <dt-bindings/interrupt-controller/arm-gic.h>
-         #include <dt-bindings/mailbox/qcom-ipcc.h>
+     #include <dt-bindings/interrupt-controller/arm-gic.h>
+     #include <dt-bindings/mailbox/qcom-ipcc.h>
  
-         mailbox@408000 {
-                 compatible = "qcom,sm8250-ipcc", "qcom,ipcc";
-                 reg = <0x408000 0x1000>;
-                 interrupts = <GIC_SPI 229 IRQ_TYPE_LEVEL_HIGH>;
-                 interrupt-controller;
-                 #interrupt-cells = <3>;
-                 #mbox-cells = <2>;
-         };
+     mailbox@408000 {
+         compatible = "qcom,sm8250-ipcc", "qcom,ipcc";
+         reg = <0x408000 0x1000>;
+         interrupts = <GIC_SPI 229 IRQ_TYPE_LEVEL_HIGH>;
+         interrupt-controller;
+         #interrupt-cells = <3>;
+         #mbox-cells = <2>;
+     };
 +
-         smp2p-modem {
-                 compatible = "qcom,smp2p";
-                 qcom,smem = <443>, <429>;
-                 interrupts-extended = <&ipcc IPCC_CLIENT_LPASS
-                                              IPCC_MPROC_SIGNAL_SMP2P
-                                              IRQ_TYPE_EDGE_RISING>;
-                 mboxes = <&ipcc IPCC_CLIENT_LPASS
-                                 IPCC_MPROC_SIGNAL_SMP2P>;
++    smp2p-modem {
++        compatible = "qcom,smp2p";
++        qcom,smem = <443>, <429>;
++        interrupts-extended = <&ipcc IPCC_CLIENT_LPASS
++                                     IPCC_MPROC_SIGNAL_SMP2P
++                                     IRQ_TYPE_EDGE_RISING>;
++        mboxes = <&ipcc IPCC_CLIENT_LPASS
++                        IPCC_MPROC_SIGNAL_SMP2P>;
 +
-                 qcom,local-pid = <0>;
-                 qcom,remote-pid = <2>;
-                 /* Other SMP2P fields */
-         };
++        qcom,local-pid = <0>;
++        qcom,remote-pid = <2>;
++        /* Other SMP2P fields */
++    };

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

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

end of thread, other threads:[~2022-05-23 14:40 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-11-28  0:41 linux-next: manual merge of the mailbox tree with the devicetree tree Stephen Rothwell
2019-11-28  9:25 ` Arnaud POULIQUEN
2022-05-23  4:05 Stephen Rothwell
2022-05-23 14:33 ` Krzysztof Kozlowski
2022-05-23 14:39   ` Rob Herring

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).