From: Rob Herring <robh@kernel.org>
To: Tony Huang <tonyhuang.sunplus@gmail.com>
Cc: tony.huang@sunplus.com, derek.kiernan@xilinx.com,
linux-kernel@vger.kernel.org, robh+dt@kernel.org,
devicetree@vger.kernel.org, dragan.cvetic@xilinx.com,
arnd@arndb.de, krzysztof.kozlowski@canonical.com,
gregkh@linuxfoundation.org, wells.lu@sunplus.com
Subject: Re: [PATCH v11 1/2] dt-bindings: misc: Add iop yaml file for Sunplus SP7021
Date: Mon, 14 Mar 2022 08:42:49 -0600 [thread overview]
Message-ID: <1647268969.313741.12505.nullmailer@robh.at.kernel.org> (raw)
In-Reply-To: <c0ef91adc0af9fedca2791e4006009fabfdfef2c.1647095774.git.tonyhuang.sunplus@gmail.com>
On Sun, 13 Mar 2022 00:16:04 +0800, Tony Huang wrote:
> Add iop yaml file for Sunplus SP7021
>
> Reviewed-by: Rob Herring <robh@kernel.org>
> Signed-off-by: Tony Huang <tonyhuang.sunplus@gmail.com>
> ---
> Changes in v11:
> - Addressed comments from krzysztof.
>
> .../devicetree/bindings/misc/sunplus,iop.yaml | 78 ++++++++++++++++++++++
> MAINTAINERS | 5 ++
> 2 files changed, 83 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/misc/sunplus,iop.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/misc/sunplus,iop.yaml:78:7: [error] no new line character at the end of file (new-line-at-end-of-file)
dtschema/dtc warnings/errors:
./Documentation/devicetree/bindings/misc/sunplus,iop.yaml: $id: relative path/filename doesn't match actual path or filename
expected: http://devicetree.org/schemas/misc/sunplus,iop.yaml#
/builds/robherring/linux-dt-review/Documentation/devicetree/bindings/misc/sunplus,iop.example.dt.yaml: iop@9c000400: 'clocks' does not match any of the regexes: 'pinctrl-[0-9]+'
From schema: /builds/robherring/linux-dt-review/Documentation/devicetree/bindings/misc/sunplus,iop.yaml
doc reference errors (make refcheckdocs):
See https://patchwork.ozlabs.org/patch/1604673
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-03-14 14:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-12 16:16 [PATCH v11 0/2] Add iop driver for Sunplus SP7021 Tony Huang
2022-03-12 16:16 ` [PATCH v11 1/2] dt-bindings: misc: Add iop yaml file " Tony Huang
2022-03-13 9:33 ` Krzysztof Kozlowski
2022-03-14 1:37 ` Tony Huang 黃懷厚
2022-03-13 9:40 ` Krzysztof Kozlowski
2022-03-14 1:39 ` Tony Huang 黃懷厚
2022-03-14 14:42 ` Rob Herring [this message]
2022-03-12 16:16 ` [PATCH v11 2/2] misc: Add iop driver " Tony Huang
2022-03-13 9:43 ` Krzysztof Kozlowski
2022-03-14 6:08 ` Tony Huang 黃懷厚
2022-03-14 7:55 ` Krzysztof Kozlowski
2022-03-15 2:08 ` Tony Huang 黃懷厚
2022-03-15 7:22 ` Krzysztof Kozlowski
2022-03-15 8:24 ` Tony Huang 黃懷厚
2022-03-15 9:22 ` Arnd Bergmann
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=1647268969.313741.12505.nullmailer@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=arnd@arndb.de \
--cc=derek.kiernan@xilinx.com \
--cc=devicetree@vger.kernel.org \
--cc=dragan.cvetic@xilinx.com \
--cc=gregkh@linuxfoundation.org \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=tony.huang@sunplus.com \
--cc=tonyhuang.sunplus@gmail.com \
--cc=wells.lu@sunplus.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