linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* linux-next: manual merge of the net-next tree with the clk tree
@ 2020-06-02  2:09 Stephen Rothwell
  2020-06-04  1:29 ` Stephen Rothwell
  0 siblings, 1 reply; 3+ messages in thread
From: Stephen Rothwell @ 2020-06-02  2:09 UTC (permalink / raw)
  To: David Miller, Networking, Mike Turquette, Stephen Boyd
  Cc: Linux Next Mailing List, Linux Kernel Mailing List, Macpaul Lin,
	Bartosz Golaszewski

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

Hi all,

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

  Documentation/devicetree/bindings/arm/mediatek/mediatek,pericfg.txt

between commit:

  7b9e111a5216 ("dt-bindings: clock: mediatek: document clk bindings for Mediatek MT6765 SoC")

from the clk tree and commit:

  9f9d1e63dc55 ("dt-bindings: convert the binding document for mediatek PERICFG to yaml")

from the net-next tree.

I fixed it up (I deleted the file and added the following patch) 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.

From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Tue, 2 Jun 2020 12:07:03 +1000
Subject: [PATCH] dt-bindings: fix up for "dt-bindings: clock: mediatek:
 document clk bindings for Mediatek MT6765 SoC"

Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
---
 .../devicetree/bindings/arm/mediatek/mediatek,pericfg.yaml       | 1 +
 1 file changed, 1 insertion(+)

diff --git a/Documentation/devicetree/bindings/arm/mediatek/mediatek,pericfg.yaml b/Documentation/devicetree/bindings/arm/mediatek/mediatek,pericfg.yaml
index 55209a2baedc..e271c4682ebc 100644
--- a/Documentation/devicetree/bindings/arm/mediatek/mediatek,pericfg.yaml
+++ b/Documentation/devicetree/bindings/arm/mediatek/mediatek,pericfg.yaml
@@ -20,6 +20,7 @@ properties:
         - enum:
           - mediatek,mt2701-pericfg
           - mediatek,mt2712-pericfg
+          - mediatek,mt6765-pericfg
           - mediatek,mt7622-pericfg
           - mediatek,mt7629-pericfg
           - mediatek,mt8135-pericfg
-- 
2.26.2

-- 
Cheers,
Stephen Rothwell

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

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

* Re: linux-next: manual merge of the net-next tree with the clk tree
  2020-06-02  2:09 linux-next: manual merge of the net-next tree with the clk tree Stephen Rothwell
@ 2020-06-04  1:29 ` Stephen Rothwell
  0 siblings, 0 replies; 3+ messages in thread
From: Stephen Rothwell @ 2020-06-04  1:29 UTC (permalink / raw)
  To: Mike Turquette, Stephen Boyd
  Cc: David Miller, Networking, Linux Next Mailing List,
	Linux Kernel Mailing List, Macpaul Lin, Bartosz Golaszewski

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

Hi all,

On Tue, 2 Jun 2020 12:09:57 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi all,
> 
> Today's linux-next merge of the net-next tree got a conflict in:
> 
>   Documentation/devicetree/bindings/arm/mediatek/mediatek,pericfg.txt
> 
> between commit:
> 
>   7b9e111a5216 ("dt-bindings: clock: mediatek: document clk bindings for Mediatek MT6765 SoC")
> 
> from the clk tree and commit:
> 
>   9f9d1e63dc55 ("dt-bindings: convert the binding document for mediatek PERICFG to yaml")
> 
> from the net-next tree.
> 
> I fixed it up (I deleted the file and added the following patch) 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.
> 
> From: Stephen Rothwell <sfr@canb.auug.org.au>
> Date: Tue, 2 Jun 2020 12:07:03 +1000
> Subject: [PATCH] dt-bindings: fix up for "dt-bindings: clock: mediatek:
>  document clk bindings for Mediatek MT6765 SoC"
> 
> Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
> ---
>  .../devicetree/bindings/arm/mediatek/mediatek,pericfg.yaml       | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/Documentation/devicetree/bindings/arm/mediatek/mediatek,pericfg.yaml b/Documentation/devicetree/bindings/arm/mediatek/mediatek,pericfg.yaml
> index 55209a2baedc..e271c4682ebc 100644
> --- a/Documentation/devicetree/bindings/arm/mediatek/mediatek,pericfg.yaml
> +++ b/Documentation/devicetree/bindings/arm/mediatek/mediatek,pericfg.yaml
> @@ -20,6 +20,7 @@ properties:
>          - enum:
>            - mediatek,mt2701-pericfg
>            - mediatek,mt2712-pericfg
> +          - mediatek,mt6765-pericfg
>            - mediatek,mt7622-pericfg
>            - mediatek,mt7629-pericfg
>            - mediatek,mt8135-pericfg
> -- 
> 2.26.2

This merge resolution patch is now needed when the clk tree merges with
Linus' tree

-- 
Cheers,
Stephen Rothwell

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

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

* linux-next: manual merge of the net-next tree with the clk tree
@ 2023-04-19 14:13 broonie
  0 siblings, 0 replies; 3+ messages in thread
From: broonie @ 2023-04-19 14:13 UTC (permalink / raw)
  To: David Miller, Networking
  Cc: Conor Dooley, Emil Renner Berthing, Hal Feng,
	Linux Kernel Mailing List, Linux Next Mailing List, Paolo Abeni,
	Samin Guo, Yanhong Wang

Hi all,

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

  MAINTAINERS

between commit:

  63a30e1f44d5e ("MAINTAINERS: generalise StarFive clk/reset entries")

from the clk tree and commit:

  b76eaf7d7ede3 ("dt-bindings: net: Add support StarFive dwmac")

from the net-next 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 MAINTAINERS
index 8c77a6a3f2c56,4fc57dfd5fd0a..0000000000000
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@@ -19911,6 -19928,20 +19937,13 @@@ M:	Emil Renner Berthing <kernel@esmil.d
  S:	Maintained
  F:	arch/riscv/boot/dts/starfive/
  
+ STARFIVE DWMAC GLUE LAYER
+ M:	Emil Renner Berthing <kernel@esmil.dk>
+ M:	Samin Guo <samin.guo@starfivetech.com>
+ S:	Maintained
+ F:	Documentation/devicetree/bindings/net/starfive,jh7110-dwmac.yaml
+ F:	drivers/net/ethernet/stmicro/stmmac/dwmac-starfive.c
+ 
 -STARFIVE JH7100 CLOCK DRIVERS
 -M:	Emil Renner Berthing <kernel@esmil.dk>
 -S:	Maintained
 -F:	Documentation/devicetree/bindings/clock/starfive,jh7100-*.yaml
 -F:	drivers/clk/starfive/clk-starfive-jh7100*
 -F:	include/dt-bindings/clock/starfive-jh7100*.h
 -
  STARFIVE JH7110 MMC/SD/SDIO DRIVER
  M:	William Qiu <william.qiu@starfivetech.com>
  S:	Supported

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

end of thread, other threads:[~2023-04-19 14:14 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-06-02  2:09 linux-next: manual merge of the net-next tree with the clk tree Stephen Rothwell
2020-06-04  1:29 ` Stephen Rothwell
2023-04-19 14:13 broonie

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).