From: Rob Herring <robh@kernel.org>
To: Aparna M <a-m1@ti.com>
Cc: grygorii.strashko@ti.com, bgolaszewski@baylibre.com,
a-govindraju@ti.com, praneeth@ti.com, robh+dt@kernel.org,
devicetree@vger.kernel.org, linus.walleij@linaro.org,
linux-gpio@vger.kernel.org
Subject: Re: [PATCH v4] dt-bindings: gpio: Convert TI TPIC2810 GPIO Controller bindings to YAML
Date: Wed, 23 Feb 2022 10:08:31 -0600 [thread overview]
Message-ID: <1645632511.483635.1021550.nullmailer@robh.at.kernel.org> (raw)
In-Reply-To: <20220223072308.31868-1-a-m1@ti.com>
On Wed, 23 Feb 2022 12:53:08 +0530, Aparna M wrote:
> Convert gpio-tpic2810 bindings to yaml format and remove outdated
> bindings in .txt format.
>
> Signed-off-by: Aparna M <a-m1@ti.com>
> ---
>
> v3 -> v4: Add gpio-line-names property
> v2 -> v3: Remove redundant descriptions and make minor change in example
> v1 -> v2: Fix identation issues and update commit message
>
> .../bindings/gpio/gpio-tpic2810.txt | 16 ------
> .../bindings/gpio/gpio-tpic2810.yaml | 51 +++++++++++++++++++
> 2 files changed, 51 insertions(+), 16 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/gpio/gpio-tpic2810.txt
> create mode 100644 Documentation/devicetree/bindings/gpio/gpio-tpic2810.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:
./Documentation/devicetree/bindings/gpio/gpio-tpic2810.yaml:10:4: [warning] wrong indentation: expected 2 but found 3 (indentation)
./Documentation/devicetree/bindings/gpio/gpio-tpic2810.yaml:30:5: [warning] wrong indentation: expected 2 but found 4 (indentation)
dtschema/dtc warnings/errors:
doc reference errors (make refcheckdocs):
See https://patchwork.ozlabs.org/patch/1596522
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.
prev parent reply other threads:[~2022-02-23 16:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 7:23 [PATCH v4] dt-bindings: gpio: Convert TI TPIC2810 GPIO Controller bindings to YAML Aparna M
2022-02-23 16:08 ` Rob Herring [this message]
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=1645632511.483635.1021550.nullmailer@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=a-govindraju@ti.com \
--cc=a-m1@ti.com \
--cc=bgolaszewski@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=grygorii.strashko@ti.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=praneeth@ti.com \
--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;
as well as URLs for NNTP newsgroup(s).