From: Rob Herring <robh@kernel.org>
To: Kavyasree Kotagiri <kavyasree.kotagiri@microchip.com>
Cc: UNGLinuxDriver@microchip.com, claudiu.beznea@microchip.com,
linux-arm-kernel@lists.infradead.org,
alexandre.belloni@bootlin.com, devicetree@vger.kernel.org,
nicolas.ferre@microchip.com, krzysztof.kozlowski+dt@linaro.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/3] dt-bindings: mfd: atmel,flexcom: Convert to json-schema
Date: Wed, 08 Jun 2022 07:45:07 -0600 [thread overview]
Message-ID: <1654695907.368178.1272082.nullmailer@robh.at.kernel.org> (raw)
In-Reply-To: <20220607144740.14937-2-kavyasree.kotagiri@microchip.com>
On Tue, 07 Jun 2022 20:17:38 +0530, Kavyasree Kotagiri wrote:
> Convert the Atmel flexcom device tree bindings to json schema.
>
> Signed-off-by: Kavyasree Kotagiri <kavyasree.kotagiri@microchip.com>
> ---
> v1 -> v2:
> - Fix title.
>
> .../bindings/mfd/atmel,flexcom.yaml | 97 +++++++++++++++++++
> .../devicetree/bindings/mfd/atmel-flexcom.txt | 63 ------------
> 2 files changed, 97 insertions(+), 63 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/mfd/atmel,flexcom.yaml
> delete mode 100644 Documentation/devicetree/bindings/mfd/atmel-flexcom.txt
>
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:
Documentation/devicetree/bindings/mfd/atmel,flexcom.example.dtb:0:0: /example-0/flexcom@f8034000/spi@400: failed to match any schema with compatible: ['atmel,at91rm9200-spi']
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-06-08 13:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 14:47 [PATCH v2 0/3] Add support for lan966x flexcom chip-select configuration Kavyasree Kotagiri
2022-06-07 14:47 ` [PATCH v2 1/3] dt-bindings: mfd: atmel,flexcom: Convert to json-schema Kavyasree Kotagiri
2022-06-08 7:25 ` Claudiu.Beznea
2022-06-08 8:34 ` Krzysztof Kozlowski
2022-06-08 9:31 ` Kavyasree.Kotagiri
2022-06-08 9:33 ` Krzysztof Kozlowski
2022-06-16 9:20 ` Kavyasree.Kotagiri
2022-06-16 13:47 ` Krzysztof Kozlowski
2022-06-08 13:45 ` Rob Herring [this message]
2022-06-07 14:47 ` [PATCH v2 2/3] dt-bindings: mfd: atmel,flexcom: Add new compatible string for lan966x Kavyasree Kotagiri
2022-06-07 14:47 ` [PATCH v2 3/3] mfd: atmel-flexcom: Add support for lan966x flexcom chip-select configuration Kavyasree Kotagiri
2022-06-08 7:35 ` Claudiu.Beznea
2022-06-08 8:20 ` Kavyasree.Kotagiri
2022-06-08 14:17 ` Claudiu.Beznea
2022-06-09 5:18 ` Kavyasree.Kotagiri
2022-06-09 13:34 ` Kavyasree.Kotagiri
2022-06-10 9:06 ` Claudiu.Beznea
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=1654695907.368178.1272082.nullmailer@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=kavyasree.kotagiri@microchip.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.ferre@microchip.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).