From: "Rob Herring (Arm)" <robh@kernel.org>
To: Wenliang Yan <wenliang202407@163.com>
Cc: christophe.jaillet@wanadoo.fr, linux@roeck-us.net,
Jonathan Corbet <corbet@lwn.net>,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
linux-kernel@vger.kernel.org, Jean Delvare <jdelvare@suse.com>,
linux-hwmon@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v6 4/4] dt-bindings:Add SQ52206 to ina2xx devicetree bindings
Date: Thu, 27 Mar 2025 09:27:26 -0500 [thread overview]
Message-ID: <174308564652.728326.9393437187243408438.robh@kernel.org> (raw)
In-Reply-To: <20250327131841.15013-5-wenliang202407@163.com>
On Thu, 27 Mar 2025 09:18:41 -0400, Wenliang Yan wrote:
> Add the sq52206 compatible to the ina2xx.yaml
>
> Signed-off-by: Wenliang Yan <wenliang202407@163.com>
> ---
>
> Add the meaning of 'shunt-gain' in SQ52206.
>
> v5->v6:add content to meet the update requirements of the ina2xx.yaml
>
> Documentation/devicetree/bindings/hwmon/ti,ina2xx.yaml | 5 +++++
> 1 file changed, 5 insertions(+)
>
My bot found errors running 'make dt_binding_check' on your patch:
yamllint warnings/errors:
dtschema/dtc warnings/errors:
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/hwmon/ti,ina2xx.yaml: allOf:1:if:properties:compatible:contains:enum: ['silergy,sy24655', 'silergy,sy24655', 'ti,ina209', 'ti,ina219', 'ti,ina220', 'ti,ina226', 'ti,ina230', 'ti,ina231', 'ti,ina237', 'ti,ina238', 'ti,ina260'] has non-unique elements
hint: "enum" must be an array of either integers or strings
from schema $id: http://devicetree.org/meta-schemas/keywords.yaml#
doc reference errors (make refcheckdocs):
See https://patchwork.ozlabs.org/project/devicetree-bindings/patch/20250327131841.15013-5-wenliang202407@163.com
The base for the series is generally the latest rc1. A different dependency
should be noted in *this* patch.
If you already ran 'make dt_binding_check' and didn't see the above
error(s), then make sure 'yamllint' is installed and dt-schema is up to
date:
pip3 install dtschema --upgrade
Please check and re-submit after running the above command yourself. Note
that DT_SCHEMA_FILES can be set to your schema file to speed up checking
your schema. However, it must be unset to test all examples with your schema.
next prev parent reply other threads:[~2025-03-27 14:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-27 13:18 [PATCH v6 0/4] hwmon:(ina238)Add support for SQ52206 Wenliang Yan
2025-03-27 13:18 ` [PATCH v6 1/4] hwmon:(ina238)Add ina238_config to save configurations for different chips Wenliang Yan
2025-03-27 13:18 ` [PATCH v6 2/4] hwmon:(ina238)Add support for SQ52206 Wenliang Yan
2025-03-27 13:18 ` [PATCH v6 3/4] hwmon:(ina238)Modify the calculation formula to adapt to different chips Wenliang Yan
2025-03-27 13:18 ` [PATCH v6 4/4] dt-bindings:Add SQ52206 to ina2xx devicetree bindings Wenliang Yan
2025-03-27 14:27 ` Rob Herring (Arm) [this message]
2025-03-27 22:53 ` Guenter Roeck
2025-03-28 10:35 ` Wenliang Yan
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=174308564652.728326.9393437187243408438.robh@kernel.org \
--to=robh@kernel.org \
--cc=christophe.jaillet@wanadoo.fr \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=jdelvare@suse.com \
--cc=krzk+dt@kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=wenliang202407@163.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