From: Conor Dooley <conor@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Conor Dooley <Conor.Dooley@microchip.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
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: Re: linux-next: manual merge of the riscv-dt tree with the renesas tree
Date: Sun, 20 Nov 2022 23:27:42 +0000 [thread overview]
Message-ID: <Y3q37h2NkupDFL+E@spud> (raw)
In-Reply-To: <20221121102318.40c58114@canb.auug.org.au>
On Mon, Nov 21, 2022 at 10:23:18AM +1100, Stephen Rothwell wrote:
> 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.
Fixup looks good to me Stephen, thanks!
>
> --
> 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:
prev parent reply other threads:[~2022-11-20 23:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-20 23:23 linux-next: manual merge of the riscv-dt tree with the renesas tree Stephen Rothwell
2022-11-20 23:27 ` Conor Dooley [this message]
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=Y3q37h2NkupDFL+E@spud \
--to=conor@kernel.org \
--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 \
--cc=sfr@canb.auug.org.au \
/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 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.