From: Rob Herring <robh@kernel.org>
To: Melody Olvera <quic_molvera@quicinc.com>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
Bhupesh Sharma <bhupesh.sharma@linaro.org>,
Stephen Boyd <sboyd@kernel.org>,
linux-mmc@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Andy Gross <agross@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/5] dt-bindings: arm: qcom: Document QDU1000/QRU1000 SoCs and boards
Date: Mon, 03 Oct 2022 08:24:48 -0500 [thread overview]
Message-ID: <166479587535.1659013.8594790600534201114.robh@kernel.org> (raw)
In-Reply-To: <20221001030641.29354-3-quic_molvera@quicinc.com>
On Fri, 30 Sep 2022 20:06:38 -0700, Melody Olvera wrote:
> Document the QDU1000 and QRU1000 SoC bindings and the boards that use
> them.
>
> Signed-off-by: Melody Olvera <quic_molvera@quicinc.com>
> ---
> Documentation/devicetree/bindings/arm/qcom.yaml | 16 ++++++++++++++++
> 1 file changed, 16 insertions(+)
>
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/arm/qcom.yaml:725:18: [error] syntax error: mapping values are not allowed here (syntax)
dtschema/dtc warnings/errors:
make[1]: *** Deleting file 'Documentation/devicetree/bindings/arm/qcom.example.dts'
Documentation/devicetree/bindings/arm/qcom.yaml:725:18: mapping values are not allowed in this context
make[1]: *** [Documentation/devicetree/bindings/Makefile:26: Documentation/devicetree/bindings/arm/qcom.example.dts] Error 1
make[1]: *** Waiting for unfinished jobs....
./Documentation/devicetree/bindings/arm/qcom.yaml:725:18: mapping values are not allowed in this context
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/arm/qcom.yaml: ignoring, error parsing file
make: *** [Makefile:1420: dt_binding_check] Error 2
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-10-03 13:25 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-01 3:06 [PATCH 0/5] Add misc support for QDU1000/QRU1000 SoCs Melody Olvera
2022-10-01 3:06 ` [PATCH 1/5] dt-bindings: firmware: scm: Add QDU1000/QRU1000 compatibles Melody Olvera
2022-10-01 9:25 ` Krzysztof Kozlowski
2022-10-03 22:02 ` Melody Olvera
2022-10-03 22:14 ` Dmitry Baryshkov
2022-10-04 6:53 ` Krzysztof Kozlowski
2022-10-04 7:36 ` Dmitry Baryshkov
2022-10-04 15:52 ` Melody Olvera
2022-10-04 16:08 ` Melody Olvera
2022-10-04 21:05 ` Dmitry Baryshkov
2022-10-05 8:27 ` Krzysztof Kozlowski
2022-10-05 21:08 ` Trilok Soni
2022-10-01 3:06 ` [PATCH 2/5] dt-bindings: arm: qcom: Document QDU1000/QRU1000 SoCs and boards Melody Olvera
2022-10-01 9:26 ` Krzysztof Kozlowski
2022-10-04 15:16 ` Melody Olvera
2022-10-03 13:24 ` Rob Herring [this message]
2022-10-01 3:06 ` [PATCH 3/5] dt-bindings: power: rpmpd: Add QDU1000/QRU1000 to rpmpd binding Melody Olvera
2022-10-01 9:27 ` Krzysztof Kozlowski
2022-10-04 15:19 ` Melody Olvera
2022-10-01 3:06 ` [PATCH 4/5] soc: qcom: rpmhpd: Add QDU1000/QRU1000 power domains Melody Olvera
2022-10-01 7:50 ` Dmitry Baryshkov
2022-10-07 3:11 ` Bjorn Andersson
2022-10-12 20:32 ` Melody Olvera
2022-10-01 3:06 ` [PATCH 5/5] soc: qcom: socinfo: Add QDU1000/QRU1000 and variant IDs Melody Olvera
2022-10-01 9:28 ` Krzysztof Kozlowski
2022-10-01 9:34 ` [PATCH 0/5] Add misc support for QDU1000/QRU1000 SoCs Krzysztof Kozlowski
2022-10-04 15:27 ` Melody Olvera
2022-10-04 16:05 ` Melody Olvera
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=166479587535.1659013.8594790600534201114.robh@kernel.org \
--to=robh@kernel.org \
--cc=agross@kernel.org \
--cc=bhupesh.sharma@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=quic_molvera@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=ulf.hansson@linaro.org \
/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