From: Conor Dooley <conor@kernel.org>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
linux-renesas-soc@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: soc: renesas: Document R-Car X5H
Date: Wed, 27 Aug 2025 18:19:31 +0100 [thread overview]
Message-ID: <20250827-donator-throwaway-57c8df9083ef@spud> (raw)
In-Reply-To: <87a53lbr9x.wl-kuninori.morimoto.gx@renesas.com>
[-- Attachment #1: Type: text/plain, Size: 937 bytes --]
On Tue, Aug 26, 2025 at 11:24:26PM +0000, Kuninori Morimoto wrote:
>
> Hi Conor
>
> Thank you for your feedback
>
> > > I have been mentioned that I will post DT-Doc when I post board
> > > support patch, but I think it will be postponeed.
> > > So I will post SoC part now.
> >
> > What's the value in posting it alone, if it requires a board to be
> > actually used?
> (snip)
> > > + - description: R-Car X5H (R8A78000)
> > > + items:
> > > + - const: renesas,r8a78000
>
> I have already posted the patch which introduce "renesas,r8a78000".
> Kernel will have DT check error/warning without this patch.
Then I suggest you add a "- {}" entry, to be replaced when the board is
added, to avoid allowing invalid use.
>
> Board support patch will be posted if these were accepted (and ready
> to post).
>
> Thank you for your help !!
>
> Best regards
> ---
> Kuninori Morimoto
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2025-08-27 17:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-26 0:06 [PATCH] dt-bindings: soc: renesas: Document R-Car X5H Kuninori Morimoto
2025-08-26 17:52 ` Conor Dooley
2025-08-26 23:24 ` Kuninori Morimoto
2025-08-27 17:19 ` 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=20250827-donator-throwaway-57c8df9083ef@spud \
--to=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=krzk+dt@kernel.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=robh@kernel.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;
as well as URLs for NNTP newsgroup(s).