From: Rob Herring <robh@kernel.org>
To: Taniya Das <tdas@codeaurora.org>
Cc: "Stephen Boyd" <sboyd@kernel.org>,
"Michael Turquette " <mturquette@baylibre.com>,
"David Brown" <david.brown@linaro.org>,
"Rajendra Nayak" <rnayak@codeaurora.org>,
linux-arm-msm@vger.kernel.org, linux-soc@vger.kernel.org,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
"Andy Gross" <agross@kernel.org>,
devicetree@vger.kernel.org, robh@kernel.org, robh+dt@kernel.org,
"Taniya Das" <tdas@codeaurora.org>
Subject: Re: [PATCH v5 3/5] dt-bindings: clock: Add YAML schemas for the QCOM MSS clock bindings
Date: Mon, 24 Feb 2020 12:42:01 -0600 [thread overview]
Message-ID: <20200224184201.GA6030@bogus> (raw)
In-Reply-To: <1582540703-6328-4-git-send-email-tdas@codeaurora.org>
On Mon, 24 Feb 2020 16:08:21 +0530, Taniya Das wrote:
> The Modem Subsystem clock provider have a bunch of generic properties
> that are needed in a device tree. Add a YAML schemas for those.
>
> Signed-off-by: Taniya Das <tdas@codeaurora.org>
> ---
> .../devicetree/bindings/clock/qcom,sc7180-mss.yaml | 62 ++++++++++++++++++++++
> 1 file changed, 62 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/clock/qcom,sc7180-mss.yaml
>
My bot found errors running 'make dt_binding_check' on your patch:
Documentation/devicetree/bindings/display/simple-framebuffer.example.dts:21.16-37.11: Warning (chosen_node_is_root): /example-0/chosen: chosen node must be at root node
Error: Documentation/devicetree/bindings/clock/qcom,sc7180-mss.example.dts:21.26-27 syntax error
FATAL ERROR: Unable to parse input tree
scripts/Makefile.lib:300: recipe for target 'Documentation/devicetree/bindings/clock/qcom,sc7180-mss.example.dt.yaml' failed
make[1]: *** [Documentation/devicetree/bindings/clock/qcom,sc7180-mss.example.dt.yaml] Error 1
Makefile:1263: recipe for target 'dt_binding_check' failed
make: *** [dt_binding_check] Error 2
See https://patchwork.ozlabs.org/patch/1242999
Please check and re-submit.
next prev parent reply other threads:[~2020-02-24 18:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-24 10:38 [PATCH v5 0/5] Add modem Clock controller (MSS CC) driver for SC7180 Taniya Das
2020-02-24 10:38 ` [PATCH v5 1/5] dt-bindings: clock: Add support for Modem clocks in GCC Taniya Das
2020-02-24 10:38 ` [PATCH v5 2/5] clk: qcom: gcc: Add support for modem " Taniya Das
2020-02-24 10:38 ` [PATCH v5 3/5] dt-bindings: clock: Add YAML schemas for the QCOM MSS clock bindings Taniya Das
2020-02-24 18:42 ` Rob Herring [this message]
2020-02-25 5:49 ` Taniya Das
2020-02-25 13:58 ` Rob Herring
[not found] ` <158267707817.177367.4165827948994155128@swboyd.mtv.corp.google.com>
2020-02-26 14:10 ` Rob Herring
2020-03-14 18:46 ` Taniya Das
2020-02-24 10:38 ` [PATCH v5 4/5] dt-bindings: clock: Introduce QCOM Modem " Taniya Das
2020-02-26 0:32 ` Stephen Boyd
2020-02-24 10:38 ` [PATCH v5 5/5] clk: qcom: Add modem clock controller driver for SC7180 Taniya Das
2020-02-26 0:20 ` Stephen Boyd
2020-02-26 0:28 ` Stephen Boyd
2020-03-09 20:06 ` [PATCH v5 0/5] Add modem Clock controller (MSS CC) " Stephen Boyd
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=20200224184201.GA6030@bogus \
--to=robh@kernel.org \
--cc=agross@kernel.org \
--cc=david.brown@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-soc@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=rnayak@codeaurora.org \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=tdas@codeaurora.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.