From: "Nuno Sá" <noname.nuno@gmail.com>
To: Rob Herring <robh@kernel.org>, Nuno Sa <nuno.sa@analog.com>
Cc: linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
Jonathan Cameron <jic23@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Michael Hennerich <Michael.Hennerich@analog.com>,
Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH v2 2/3] dt-bindings: iio: temperature: ltc2983: document power supply
Date: Fri, 01 Mar 2024 08:16:52 +0100 [thread overview]
Message-ID: <af4539ebb5786d1f93c3d9b2b427412838e75160.camel@gmail.com> (raw)
In-Reply-To: <170922758600.4099132.651212743562426191.robh@kernel.org>
On Thu, 2024-02-29 at 11:26 -0600, Rob Herring wrote:
>
> On Thu, 29 Feb 2024 17:11:42 +0100, Nuno Sa wrote:
> > Add a property for the VDD power supply regulator.
> >
> > Signed-off-by: Nuno Sa <nuno.sa@analog.com>
> > ---
> > Documentation/devicetree/bindings/iio/temperature/adi,ltc2983.yaml | 3 +++
> > 1 file changed, 3 insertions(+)
> >
>
> 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/iio/temperature/adi,ltc2983.example.dtb:
> temperature-sensor@0: 'vdd-supply' is a required property
> from schema $id:
> http://devicetree.org/schemas/iio/temperature/adi,ltc2983.yaml#
>
> doc reference errors (make refcheckdocs):
>
> See
> https://patchwork.ozlabs.org/project/devicetree-bindings/patch/20240229-ltc2983-misc-improv-v2-2-cc6f03da2529@analog.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.
>
Damn!!!! I'll send a v3 fixing this...
- Nuno Sá
next prev parent reply other threads:[~2024-03-01 7:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 16:11 [PATCH v2 0/3] iio: temperature: ltc2983: small improvements Nuno Sa
2024-02-29 16:11 ` [PATCH v2 1/3] iio: temperature: ltc2983: convert to dev_err_probe() Nuno Sa
2024-02-29 16:11 ` [PATCH v2 2/3] dt-bindings: iio: temperature: ltc2983: document power supply Nuno Sa
2024-02-29 17:26 ` Rob Herring
2024-03-01 7:16 ` Nuno Sá [this message]
2024-02-29 16:11 ` [PATCH v2 3/3] iio: temperature: ltc2983: support vdd regulator Nuno Sa
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=af4539ebb5786d1f93c3d9b2b427412838e75160.camel@gmail.com \
--to=noname.nuno@gmail.com \
--cc=Michael.Hennerich@analog.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=robh+dt@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).