From: Liang Yang <liang.yang@amlogic.com>
To: Rob Herring <robh@kernel.org>
Cc: Vignesh Raghavendra <vigneshr@ti.com>,
Kelvin Zhang <kelvin.zhang@amlogic.com>,
Richard Weinberger <richard@nod.at>,
XianWei Zhao <xianwei.zhao@amlogic.com>,
Kevin Hilman <khilman@baylibre.com>,
BiChao Zheng <bichao.zheng@amlogic.com>,
Neil Armstrong <narmstrong@baylibre.com>,
Rob Herring <robh+dt@kernel.org>,
Jianxin Pan <jianxin.pan@amlogic.com>,
<linux-amlogic@lists.infradead.org>,
Jerome Brunet <jbrunet@baylibre.com>,
<linux-kernel@vger.kernel.org>,
Victor Wan <victor.wan@amlogic.com>,
<linux-mtd@lists.infradead.org>,
Miquel Raynal <miquel.raynal@bootlin.com>,
<devicetree@vger.kernel.org>, YongHui Yu <yonghui.yu@amlogic.com>,
<linux-arm-kernel@lists.infradead.org>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Subject: Re: [PATCH RESEND v8 4/5] dt-bindings: nand: meson: convert txt to yaml
Date: Wed, 7 Sep 2022 15:43:14 +0800 [thread overview]
Message-ID: <ea0dda97-2f53-0a3f-6168-18b20a4095c0@amlogic.com> (raw)
In-Reply-To: <1662471645.297810.360952.nullmailer@robh.at.kernel.org>
Hi Rob,
I reproduce this error and will fix it next version.
Thanks.
On 2022/9/6 21:40, Rob Herring wrote:
> [ EXTERNAL EMAIL ]
>
> On Tue, 06 Sep 2022 14:00:32 +0800, Liang Yang wrote:
>> convert the amlogic,meson-name.txt to amlogic,meson-nand.yaml
>>
>> Signed-off-by: Liang Yang <liang.yang@amlogic.com>
>> ---
>> .../bindings/mtd/amlogic,meson-nand.txt | 55 ------------
>> .../bindings/mtd/amlogic,meson-nand.yaml | 88 +++++++++++++++++++
>> 2 files changed, 88 insertions(+), 55 deletions(-)
>> delete mode 100644 Documentation/devicetree/bindings/mtd/amlogic,meson-nand.txt
>> create mode 100644 Documentation/devicetree/bindings/mtd/amlogic,meson-nand.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/linux-dt-review/Documentation/devicetree/bindings/mtd/amlogic,meson-nand.example.dtb: nand-controller@ffe07800: Unevaluated properties are not allowed ('reg-names' was unexpected)
> From schema: /builds/robherring/linux-dt-review/Documentation/devicetree/bindings/mtd/amlogic,meson-nand.yaml
>
> doc reference errors (make refcheckdocs):
> MAINTAINERS: Documentation/devicetree/bindings/mtd/amlogic,meson-nand.txt
>
> 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-09-07 7:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-06 6:00 [PATCH RESEND v8 0/5] fix the meson NFC clock Liang Yang
2022-09-06 6:00 ` [PATCH RESEND v8 1/5] dt-bindings: nand: meson: fix meson nfc clock Liang Yang
2022-09-06 6:00 ` [PATCH RESEND v8 2/5] mtd: rawnand: meson: fix the clock Liang Yang
2022-09-06 6:00 ` [PATCH RESEND v8 3/5] mtd: rawnand: meson: refine resource getting in probe Liang Yang
2022-09-06 6:00 ` [PATCH RESEND v8 4/5] dt-bindings: nand: meson: convert txt to yaml Liang Yang
2022-09-06 13:40 ` Rob Herring
2022-09-07 7:43 ` Liang Yang [this message]
2022-09-06 14:30 ` Rob Herring
2022-09-07 7:45 ` Liang Yang
2022-09-06 6:00 ` [PATCH RESEND v8 5/5] mtd: rawnand: meson: not support legacy clock Liang Yang
-- strict thread matches above, loose matches on Subject: below --
2022-09-05 7:50 [PATCH RESEND v8 0/5] fix the meson NFC clock Liang Yang
2022-09-05 7:50 ` [PATCH RESEND v8 4/5] dt-bindings: nand: meson: convert txt to yaml Liang Yang
2022-08-22 9:18 [PATCH RESEND v8 0/5] fix the meson NFC clock Liang Yang
2022-08-22 9:18 ` [PATCH RESEND v8 4/5] dt-bindings: nand: meson: convert txt to yaml Liang Yang
2022-09-05 7:22 ` Neil Armstrong
2022-09-05 7:37 ` Liang Yang
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=ea0dda97-2f53-0a3f-6168-18b20a4095c0@amlogic.com \
--to=liang.yang@amlogic.com \
--cc=bichao.zheng@amlogic.com \
--cc=devicetree@vger.kernel.org \
--cc=jbrunet@baylibre.com \
--cc=jianxin.pan@amlogic.com \
--cc=kelvin.zhang@amlogic.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=miquel.raynal@bootlin.com \
--cc=narmstrong@baylibre.com \
--cc=richard@nod.at \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=victor.wan@amlogic.com \
--cc=vigneshr@ti.com \
--cc=xianwei.zhao@amlogic.com \
--cc=yonghui.yu@amlogic.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).