From: Rob Herring <robh@kernel.org>
To: "Martin Zaťovič" <m.zatovic1@gmail.com>
Cc: krzysztof.kozlowski+dt@linaro.org, devicetree@vger.kernel.org,
jeffrey.l.hugo@gmail.com, hemantk@codeaurora.org,
f.fainelli@gmail.com, bjorn.andersson@linaro.org,
gregkh@linuxfoundation.org, mani@kernel.org,
saravanak@google.com, Michael.Srba@seznam.cz,
linux-kernel@vger.kernel.org, robh+dt@kernel.org,
elder@linaro.org, linus.walleij@linaro.org
Subject: Re: [PATCH RFC v1 2/2] devicetree: bindings: bus: add Wiegand driver documentation
Date: Thu, 28 Jul 2022 07:47:12 -0600 [thread overview]
Message-ID: <1659016032.636583.779711.nullmailer@robh.at.kernel.org> (raw)
In-Reply-To: <20220728091712.13395-2-m.zatovic1@gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1444 bytes --]
On Thu, 28 Jul 2022 11:17:12 +0200, Martin Zaťovič wrote:
> Wiegand write-only driver requires definitions of two GPIO lines
> in the devicetree. This adds the documentation of their
> definitions.
>
> Signed-off-by: Martin Zaťovič <m.zatovic1@gmail.com>
> ---
> .../devicetree/bindings/bus/wiegand-gpio.yaml | 66 +++++++++++++++++++
> MAINTAINERS | 1 +
> 2 files changed, 67 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/bus/wiegand-gpio.yaml
>
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:
Error: Documentation/devicetree/bindings/bus/wiegand-gpio.example.dts:22.47-48 syntax error
FATAL ERROR: Unable to parse input tree
make[1]: *** [scripts/Makefile.lib:383: Documentation/devicetree/bindings/bus/wiegand-gpio.example.dtb] Error 1
make[1]: *** Waiting for unfinished jobs....
make: *** [Makefile:1404: dt_binding_check] Error 2
doc reference errors (make refcheckdocs):
See https://patchwork.ozlabs.org/patch/
This check can fail if there are any dependencies. The base for a patch
series is generally the most recent rc1.
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.
next prev parent reply other threads:[~2022-07-28 13:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-28 9:17 [PATCH RFC v1 1/2] bus: add Wiegand write-only GPIO driver Martin Zaťovič
2022-07-28 9:17 ` [PATCH RFC v1 2/2] devicetree: bindings: bus: add Wiegand driver documentation Martin Zaťovič
2022-07-28 10:15 ` Krzysztof Kozlowski
2022-07-28 13:47 ` Rob Herring [this message]
2022-07-28 16:43 ` Krzysztof Kozlowski
2022-08-22 7:21 ` Linus Walleij
2022-07-28 9:56 ` [PATCH RFC v1 1/2] bus: add Wiegand write-only GPIO driver Greg KH
2022-07-28 10:05 ` Greg KH
2022-07-28 10:32 ` Krzysztof Kozlowski
2022-08-22 7:14 ` Linus Walleij
[not found] ` <CAPGNi94R6bW80Yc=B5iesW=ihxy_bD1p-iPhLCASh_=82mjT9w@mail.gmail.com>
2022-09-20 9:44 ` Linus Walleij
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=1659016032.636583.779711.nullmailer@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=Michael.Srba@seznam.cz \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=elder@linaro.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hemantk@codeaurora.org \
--cc=jeffrey.l.hugo@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.zatovic1@gmail.com \
--cc=mani@kernel.org \
--cc=robh+dt@kernel.org \
--cc=saravanak@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;
as well as URLs for NNTP newsgroup(s).