From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: Tomer Maimon <tmaimon77@gmail.com>
Cc: "Rob Herring (Arm)" <robh@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
venture@google.com, yuenn@google.com, openbmc@lists.ozlabs.org,
benjaminfair@google.com, joel@jms.id.au, krzk+dt@kernel.org,
tali.perry1@gmail.com, conor+dt@kernel.org,
avifishman70@gmail.com
Subject: Re: [PATCH v3 0/3] arm64: dts: nuvoton: add NPCM845 SoC and EVB support
Date: Wed, 01 Oct 2025 12:05:38 +0930 [thread overview]
Message-ID: <045c7bcd3a852e626f11e5b78c07939feac0e298.camel@codeconstruct.com.au> (raw)
In-Reply-To: <CAP6Zq1jmmhqYu3C7KHFK2tz9zjW352Bbw4cXeOYSjNSTELrp5Q@mail.gmail.com>
On Mon, 2025-09-29 at 12:15 +0300, Tomer Maimon wrote:
> Hi Rob,
>
> Thanks for your comments
>
> Most of the warnings occur because the compatible strings are located
> in .txt device tree binding rather than in the .yaml file.
>
> The only change that needs to be done is in ti,tmp100 that
>
> Could you approve the patches, avoiding NPCM845 compatible warnings?
> Meanwhile, I will work on converting the txt to yaml
I think it's best we get the conversion done, and then subsequently
apply the apply this series. See:
https://docs.kernel.org/process/maintainer-soc.html#validating-devicetree-files
and
https://docs.kernel.org/process/maintainer-soc-clean-dts.html#strict-dts-dt-schema-and-dtc-compliance
Andrew
next prev parent reply other threads:[~2025-10-01 2:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-25 20:06 Tomer Maimon
2025-09-25 20:06 ` [PATCH v3 1/3] arm64: dts: nuvoton: fix warning and nodes order Tomer Maimon
2025-10-19 10:35 ` Krzysztof Kozlowski
[not found] ` <CAP6Zq1i7repVa1oAVpyZxWw12-dv0MrVbkfXoqCKga+rp7=8LQ@mail.gmail.com>
2025-10-19 16:52 ` Krzysztof Kozlowski
2025-09-25 20:06 ` [PATCH v3 2/3] arm64: dts: nuvoton: npcm845: Add peripheral nodes Tomer Maimon
2025-09-25 20:06 ` [PATCH v3 3/3] arm64: dts: nuvoton: npcm845-evb: " Tomer Maimon
2025-09-26 16:11 ` [PATCH v3 0/3] arm64: dts: nuvoton: add NPCM845 SoC and EVB support Rob Herring (Arm)
2025-09-29 9:15 ` Tomer Maimon
2025-10-01 2:35 ` Andrew Jeffery [this message]
2025-10-16 9:06 ` Tomer Maimon
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=045c7bcd3a852e626f11e5b78c07939feac0e298.camel@codeconstruct.com.au \
--to=andrew@codeconstruct.com.au \
--cc=avifishman70@gmail.com \
--cc=benjaminfair@google.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openbmc@lists.ozlabs.org \
--cc=robh@kernel.org \
--cc=tali.perry1@gmail.com \
--cc=tmaimon77@gmail.com \
--cc=venture@google.com \
--cc=yuenn@google.com \
/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®