public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Conor Dooley <Conor.Dooley@microchip.com>,
	Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
	Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Samuel Holland <samuel@sholland.org>
Subject: linux-next: manual merge of the riscv-dt tree with the renesas tree
Date: Mon, 21 Nov 2022 10:23:18 +1100	[thread overview]
Message-ID: <20221121102318.40c58114@canb.auug.org.au> (raw)

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

Hi all,

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

  Documentation/devicetree/bindings/riscv/cpus.yaml

between commit:

  57e1b873c2f5 ("dt-bindings: riscv: Sort the CPU core list alphabetically")

from the renesas tree and commit:

  41adc2fbad8b ("dt-bindings: riscv: Add T-HEAD C906 and C910 compatibles")

from the riscv-dt 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/riscv/cpus.yaml
index 2bf91829c8de,e98a716c6f18..000000000000
--- a/Documentation/devicetree/bindings/riscv/cpus.yaml
+++ b/Documentation/devicetree/bindings/riscv/cpus.yaml
@@@ -34,12 -33,14 +34,14 @@@ properties
                - sifive,e5
                - sifive,e7
                - sifive,e71
 -              - sifive,u74-mc
 -              - sifive,u54
 -              - sifive,u74
 +              - sifive,rocket0
                - sifive,u5
 +              - sifive,u54
                - sifive,u7
 -              - canaan,k210
 +              - sifive,u74
 +              - sifive,u74-mc
+               - thead,c906
+               - thead,c910
            - const: riscv
        - items:
            - enum:

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

             reply	other threads:[~2022-11-20 23:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-20 23:23 Stephen Rothwell [this message]
2022-11-20 23:27 ` linux-next: manual merge of the riscv-dt tree with the renesas tree Conor Dooley

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20221121102318.40c58114@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=Conor.Dooley@microchip.com \
    --cc=geert+renesas@glider.be \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
    --cc=samuel@sholland.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox