From: Rob Herring <robh@kernel.org>
To: Prathamesh Shete <pshete@nvidia.com>
Cc: jonathanh@nvidia.com, linux-tegra@vger.kernel.org,
thierry.reding@gmail.com, krzysztof.kozlowski+dt@linaro.org,
linux-gpio@vger.kernel.org, linus.walleij@linaro.org,
smangipudi@nvidia.com, robh+dt@kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v2 1/3] dt-bindings: pinctrl: tegra234
Date: Wed, 08 Mar 2023 08:06:21 -0600 [thread overview]
Message-ID: <167828360289.2613214.7109201794709064028.robh@kernel.org> (raw)
In-Reply-To: <20230308114432.27133-1-pshete@nvidia.com>
On Wed, 08 Mar 2023 17:14:30 +0530, Prathamesh Shete wrote:
> Add DT binding doc for Tegra234 pinmux driver.
>
> Signed-off-by: Prathamesh Shete <pshete@nvidia.com>
> ---
> .../pinctrl/nvidia,tegra234-pinmux.yaml | 232 ++++++++++++++++++
> 1 file changed, 232 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/pinctrl/nvidia,tegra234-pinmux.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:
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/pinctrl/nvidia,tegra234-pinmux.example.dtb: pinmux@2430000: 'pinmux-pex-rst-c5-out' does not match any of the regexes: '^pinmux(-[a-z0-9]+)?$', 'pinctrl-[0-9]+'
From schema: /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/pinctrl/nvidia,tegra234-pinmux.yaml
doc reference errors (make refcheckdocs):
See https://patchwork.ozlabs.org/project/devicetree-bindings/patch/20230308114432.27133-1-pshete@nvidia.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.
prev parent reply other threads:[~2023-03-08 14:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-08 11:44 [PATCH v2 1/3] dt-bindings: pinctrl: tegra234 Prathamesh Shete
2023-03-08 11:44 ` [PATCH v2 2/3] pinctrl: tegra: Add Tegra234 pinmux driver Prathamesh Shete
2023-03-08 11:44 ` [PATCH v2 3/3] arm64: tegra: Add Tegra234 pinmux device Prathamesh Shete
2023-03-08 13:16 ` [PATCH v2 1/3] dt-bindings: pinctrl: tegra234 Krzysztof Kozlowski
2023-03-08 14:06 ` 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=167828360289.2613214.7109201794709064028.robh@kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=pshete@nvidia.com \
--cc=robh+dt@kernel.org \
--cc=smangipudi@nvidia.com \
--cc=thierry.reding@gmail.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