From: Rob Herring <robh@kernel.org>
To: "André Apitzsch" <git@apitzsch.eu>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Mark Brown <broonie@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [PATCH] dt-bindings: regulator: Convert ti,tps65133 to YAML
Date: Sun, 17 Dec 2023 08:24:42 -0600 [thread overview]
Message-ID: <170282308261.876422.2237767392476986368.robh@kernel.org> (raw)
In-Reply-To: <20231217-tps65132-v1-1-73c69a960d28@apitzsch.eu>
On Sun, 17 Dec 2023 14:21:39 +0100, André Apitzsch wrote:
> Convert TI TPS65132 bindings from .txt to .yaml format.
>
> Signed-off-by: André Apitzsch <git@apitzsch.eu>
> ---
> Note, we still have to find a person willing to be listed as maintainer.
> Suggestions are welcome.
> ---
> .../devicetree/bindings/regulator/ti,tps65132.yaml | 81 ++++++++++++++++++++++
> .../bindings/regulator/tps65132-regulator.txt | 46 ------------
> 2 files changed, 81 insertions(+), 46 deletions(-)
>
My bot found errors running 'make DT_CHECKER_FLAGS=-m dt_binding_check'
on your patch (DT_CHECKER_FLAGS is new in v5.13):
yamllint warnings/errors:
dtschema/dtc warnings/errors:
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/regulator/ti,tps65132.yaml: 'maintainers' is a required property
hint: Metaschema for devicetree binding documentation
from schema $id: http://devicetree.org/meta-schemas/base.yaml#
doc reference errors (make refcheckdocs):
See https://patchwork.ozlabs.org/project/devicetree-bindings/patch/20231217-tps65132-v1-1-73c69a960d28@apitzsch.eu
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:[~2023-12-17 14:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-17 13:21 André Apitzsch
2023-12-17 14:24 ` Rob Herring [this message]
2023-12-22 7:50 ` André Apitzsch
2023-12-22 14:49 ` Mark Brown
2023-12-23 14:17 ` Krzysztof Kozlowski
2023-12-28 17:40 ` Mark Brown
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=170282308261.876422.2237767392476986368.robh@kernel.org \
--to=robh@kernel.org \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=git@apitzsch.eu \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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
all inboxes | Powered by JetHome®