From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Rob Herring <robherring2@gmail.com>,
Wim Van Sebroeck <wim@iguana.be>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: Re: linux-next: manual merge of the devicetree tree with the watchdog tree
Date: Tue, 26 May 2020 09:00:16 +0200 [thread overview]
Message-ID: <CAMuHMdWZhpUghStL3PR4Xwp6CHjSYDj2Ap-YCPzRoKeChu8U-Q@mail.gmail.com> (raw)
In-Reply-To: <20200526152015.60b5bfd9@canb.auug.org.au>
Hi Stephen,
On Tue, May 26, 2020 at 7:20 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Today's linux-next merge of the devicetree tree got a conflict in:
>
> Documentation/devicetree/bindings/watchdog/renesas,wdt.txt
>
> between commit:
>
> ff1ee6fb276c ("dt-bindings: watchdog: renesas,wdt: Document r8a7742 support")
>
> from the watchdog tree and commit:
>
> d0941cfb9fa8 ("dt-bindings: watchdog: renesas-wdt: Convert to json-schema")
>
> from the devicetree tree.
>
> I fixed it up (I removed the file and added the patch 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.
>
> From: Stephen Rothwell <sfr@canb.auug.org.au>
> Date: Tue, 26 May 2020 15:15:51 +1000
> Subject: [PATCH] dt-bindings: watchdog: renesas-wdt: fix up for yaml conversion
>
> Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
> ---
> Documentation/devicetree/bindings/watchdog/renesas,wdt.yaml | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/devicetree/bindings/watchdog/renesas,wdt.yaml b/Documentation/devicetree/bindings/watchdog/renesas,wdt.yaml
> index 27e8c4accd67..572f4c912fef 100644
> --- a/Documentation/devicetree/bindings/watchdog/renesas,wdt.yaml
> +++ b/Documentation/devicetree/bindings/watchdog/renesas,wdt.yaml
> @@ -24,6 +24,7 @@ properties:
>
> - items:
> - enum:
> + - renesas,r8a7742-wdt # RZ/G1H
> - renesas,r8a7743-wdt # RZ/G1M
> - renesas,r8a7744-wdt # RZ/G1N
> - renesas,r8a7745-wdt # RZ/G1E
Thank you, looks good to me.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
prev parent reply other threads:[~2020-05-26 7:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-26 5:20 Stephen Rothwell
2020-05-26 7:00 ` Geert Uytterhoeven [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=CAMuHMdWZhpUghStL3PR4Xwp6CHjSYDj2Ap-YCPzRoKeChu8U-Q@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=geert+renesas@glider.be \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=robherring2@gmail.com \
--cc=sfr@canb.auug.org.au \
--cc=wim@iguana.be \
/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
all inboxes | Powered by JetHome®