From: Rob Herring <robh@kernel.org>
To: "Chia-Wei, Wang" <chiawei_wang@aspeedtech.com>
Cc: devicetree@vger.kernel.org, linux-aspeed@lists.ozlabs.org,
BMC-SW@aspeedtech.com, andrew@aj.id.au, maz@kernel.org,
openbmc@lists.ozlabs.org, linux-kernel@vger.kernel.org,
robh+dt@kernel.org, joel@jms.id.au, p.zabel@pengutronix.de,
tglx@linutronix.de, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/6] dt-bindings: aspeed: Add eSPI controller
Date: Wed, 06 Jan 2021 08:07:55 -0700 [thread overview]
Message-ID: <1609945675.315536.2229518.nullmailer@robh.at.kernel.org> (raw)
In-Reply-To: <20210106055939.19386-2-chiawei_wang@aspeedtech.com>
On Wed, 06 Jan 2021 13:59:34 +0800, Chia-Wei, Wang wrote:
> Add dt-bindings and the inclusion header for Aspeed eSPI controller.
>
> Signed-off-by: Chia-Wei, Wang <chiawei_wang@aspeedtech.com>
> ---
> .../devicetree/bindings/soc/aspeed/espi.yaml | 252 ++++++++++++++++++
> .../interrupt-controller/aspeed-espi-ic.h | 15 ++
> 2 files changed, 267 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/soc/aspeed/espi.yaml
> create mode 100644 include/dt-bindings/interrupt-controller/aspeed-espi-ic.h
>
My bot found errors running 'make dt_binding_check' on your patch:
yamllint warnings/errors:
dtschema/dtc warnings/errors:
Error: Documentation/devicetree/bindings/soc/aspeed/espi.example.dts:45.35-36 syntax error
FATAL ERROR: Unable to parse input tree
make[1]: *** [scripts/Makefile.lib:344: Documentation/devicetree/bindings/soc/aspeed/espi.example.dt.yaml] Error 1
make: *** [Makefile:1370: dt_binding_check] Error 2
See https://patchwork.ozlabs.org/patch/1422809
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.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-01-06 15:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210106055939.19386-1-chiawei_wang@aspeedtech.com>
[not found] ` <20210106055939.19386-6-chiawei_wang@aspeedtech.com>
2021-01-06 7:51 ` [PATCH 5/6] soc: aspeed: Add eSPI driver kernel test robot
2021-01-06 15:32 ` Rob Herring
2021-01-07 2:35 ` ChiaWei Wang
2021-01-08 2:59 ` Joel Stanley
2021-01-08 3:09 ` Ryan Chen
[not found] ` <20210106055939.19386-5-chiawei_wang@aspeedtech.com>
2021-01-06 10:59 ` [PATCH 4/6] irqchip/aspeed: Add Aspeed eSPI interrupt controller Marc Zyngier
2021-01-07 2:59 ` ChiaWei Wang
2021-01-07 10:17 ` Marc Zyngier
2021-01-08 2:33 ` ChiaWei Wang
[not found] ` <20210106055939.19386-2-chiawei_wang@aspeedtech.com>
2021-01-06 15:07 ` Rob Herring [this message]
2021-01-07 2:31 ` [PATCH 1/6] dt-bindings: aspeed: Add eSPI controller ChiaWei Wang
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=1609945675.315536.2229518.nullmailer@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=BMC-SW@aspeedtech.com \
--cc=andrew@aj.id.au \
--cc=chiawei_wang@aspeedtech.com \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=openbmc@lists.ozlabs.org \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=tglx@linutronix.de \
/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).