From: "Rob Herring (Arm)" <robh@kernel.org>
To: Naresh Solanki <naresh.solanki@9elements.com>
Cc: Guenter Roeck <linux@roeck-us.net>,
Liam Girdwood <lgirdwood@gmail.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
devicetree@vger.kernel.org, broonie@kernel.org,
linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org,
Conor Dooley <conor+dt@kernel.org>,
Jean Delvare <jdelvare@suse.com>
Subject: Re: [PATCH 1/2] dt-bindings: hwmon: ir38060: Move & update dt binding
Date: Tue, 04 Feb 2025 17:34:23 -0600 [thread overview]
Message-ID: <173871195460.3830123.16015645611283640170.robh@kernel.org> (raw)
In-Reply-To: <20250204180306.2755444-1-naresh.solanki@9elements.com>
On Tue, 04 Feb 2025 23:33:03 +0530, Naresh Solanki wrote:
> Move dt binding under hwmon/pmbus & align accordingly.
>
> Signed-off-by: Naresh Solanki <naresh.solanki@9elements.com>
> ---
> .../hwmon/pmbus/infineon,ir38060.yaml | 61 +++++++++++++++++++
> .../bindings/regulator/infineon,ir38060.yaml | 45 --------------
> 2 files changed, 61 insertions(+), 45 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/hwmon/pmbus/infineon,ir38060.yaml
> delete mode 100644 Documentation/devicetree/bindings/regulator/infineon,ir38060.yaml
>
My bot found new DTB warnings on the .dts files added or changed in this
series.
Some warnings may be from an existing SoC .dtsi. Or perhaps the warnings
are fixed by another series. Ultimately, it is up to the platform
maintainer whether these warnings are acceptable or not. No need to reply
unless the platform maintainer has comments.
If you already ran DT checks and didn't see these error(s), then
make sure dt-schema is up to date:
pip3 install dtschema --upgrade
New warnings running 'make CHECK_DTBS=y for arch/arm/boot/dts/aspeed/' for 20250204180306.2755444-1-naresh.solanki@9elements.com:
arch/arm/boot/dts/aspeed/aspeed-bmc-vegman-n110.dtb: /ahb/apb/display@1e6e6000: failed to match any schema with compatible: ['aspeed,ast2500-gfx', 'syscon']
arch/arm/boot/dts/aspeed/aspeed-bmc-ibm-rainier-1s4u.dtb: /ahb/apb/fsi@1e79b000/cfam@0,0/hub@3400/cfam@2,0/i2c@1800: failed to match any schema with compatible: ['ibm,fsi-i2c-master']
next prev parent reply other threads:[~2025-02-04 23:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-04 18:03 [PATCH 1/2] dt-bindings: hwmon: ir38060: Move & update dt binding Naresh Solanki
2025-02-04 18:03 ` [PATCH 2/2] ARM: dts: aspeed: sbp1: Update for ir38640 Naresh Solanki
2025-02-04 19:22 ` [PATCH 1/2] dt-bindings: hwmon: ir38060: Move & update dt binding Conor Dooley
2025-02-05 10:21 ` Naresh Solanki
2025-02-05 20:13 ` Conor Dooley
2025-02-06 15:53 ` Naresh Solanki
2025-02-06 18:09 ` Conor Dooley
2025-02-06 19:10 ` Naresh Solanki
2025-02-07 0:05 ` Conor Dooley
2025-02-12 10:43 ` Andrew Jeffery
2025-02-12 14:46 ` Guenter Roeck
2025-02-13 0:25 ` Andrew Jeffery
2025-02-12 18:56 ` Conor Dooley
2025-02-13 0:33 ` Andrew Jeffery
2025-02-04 23:34 ` Rob Herring (Arm) [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-07 13:28 Naresh Solanki
2025-02-07 15:21 ` Rob Herring (Arm)
2025-02-12 17:57 ` Rob Herring
2025-02-12 18:33 ` 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=173871195460.3830123.16015645611283640170.robh@kernel.org \
--to=robh@kernel.org \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jdelvare@suse.com \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=naresh.solanki@9elements.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