From: Rob Herring <robh@kernel.org>
To: gabriel.fernandez@foss.st.com
Cc: Stephen Boyd <sboyd@kernel.org>,
linux-clk@vger.kernel.org,
Alexandre Torgue <alexandre.torgue@st.com>,
Rob Herring <robh+dt@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Etienne Carriere <etienne.carriere@st.com>,
devicetree@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
Michael Turquette <mturquette@baylibre.com>,
linux-arm-kernel@lists.infradead.org,
Philipp Zabel <p.zabel@pengutronix.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 13/14] dt-bindings: clock: stm32mp1 new compatible for secure rcc
Date: Fri, 22 Jan 2021 08:00:45 -0600 [thread overview]
Message-ID: <1611324045.701742.674374.nullmailer@robh.at.kernel.org> (raw)
In-Reply-To: <20210122105101.27374-14-gabriel.fernandez@foss.st.com>
On Fri, 22 Jan 2021 11:51:00 +0100, gabriel.fernandez@foss.st.com wrote:
> From: Gabriel Fernandez <gabriel.fernandez@foss.st.com>
>
> Introduce new compatible string "st,stm32mp1-rcc-secure" for
> stm32mp1 clock driver when the device is configured with RCC
> security support hardened.
>
> Signed-off-by: Etienne Carriere <etienne.carriere@st.com>
> Signed-off-by: Gabriel Fernandez <gabriel.fernandez@foss.st.com>
> ---
> Documentation/devicetree/bindings/clock/st,stm32mp1-rcc.yaml | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
My bot found errors running 'make dt_binding_check' on your patch:
yamllint warnings/errors:
dtschema/dtc warnings/errors:
/builds/robherring/linux-dt-review/Documentation/devicetree/bindings/clock/st,stm32mp1-rcc.example.dt.yaml: rcc@50000000: compatible:1: 'st,stm32mp1-rcc' was expected
From schema: /builds/robherring/linux-dt-review/Documentation/devicetree/bindings/clock/st,stm32mp1-rcc.yaml
/builds/robherring/linux-dt-review/Documentation/devicetree/bindings/clock/st,stm32mp1-rcc.example.dt.yaml: rcc@50000000: compatible: ['st,stm32mp1-rcc-secure', 'syscon'] is too short
From schema: /builds/robherring/linux-dt-review/Documentation/devicetree/bindings/clock/st,stm32mp1-rcc.yaml
See https://patchwork.ozlabs.org/patch/1430316
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:[~2021-01-22 14:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-22 10:50 [PATCH 00/14] Introduce STM32MP1 RCC in secured mode gabriel.fernandez
2021-01-22 10:50 ` [PATCH 01/14] clk: stm32mp1: merge 'clk-hsi-div' and 'ck_hsi' into one clock gabriel.fernandez
2021-01-22 10:50 ` [PATCH 02/14] clk: stm32mp1: merge 'ck_hse_rtc' and 'ck_rtc' " gabriel.fernandez
2021-01-22 10:50 ` [PATCH 03/14] clk: stm32mp1: remove intermediate pll clocks gabriel.fernandez
2021-01-22 10:50 ` [PATCH 04/14] clk: stm32mp1: convert to module driver gabriel.fernandez
2021-01-22 10:50 ` [PATCH 05/14] clk: stm32mp1: move RCC reset controller into RCC clock driver gabriel.fernandez
2021-01-22 10:50 ` [PATCH 06/14] reset: stm32mp1: remove stm32mp1 reset gabriel.fernandez
2021-01-22 10:50 ` [PATCH 07/14] dt-bindings: clock: add IDs for SCMI clocks on stm32mp15 gabriel.fernandez
2021-01-22 10:50 ` [PATCH 08/14] dt-bindings: reset: add IDs for SCMI reset domains " gabriel.fernandez
2021-01-22 10:50 ` [PATCH 09/14] dt-bindings: reset: add MCU HOLD BOOT ID " gabriel.fernandez
2021-01-22 10:50 ` [PATCH 10/14] clk: stm32mp1: new compatible for secure RCC support gabriel.fernandez
2021-01-22 10:50 ` [PATCH 11/14] ARM: dts: stm32: define SCMI resources on stm32mp15 gabriel.fernandez
2021-01-22 10:50 ` [PATCH 12/14] ARM: dts: stm32: move clocks/resets to SCMI resources for stm32mp15 gabriel.fernandez
2021-01-22 10:51 ` [PATCH 13/14] dt-bindings: clock: stm32mp1 new compatible for secure rcc gabriel.fernandez
2021-01-22 14:00 ` Rob Herring [this message]
2021-01-25 13:22 ` gabriel.fernandez
2021-01-22 10:51 ` [PATCH 14/14] ARM: dts: stm32: introduce basic boot include on stm32mp15x board gabriel.fernandez
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=1611324045.701742.674374.nullmailer@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=alexandre.torgue@st.com \
--cc=devicetree@vger.kernel.org \
--cc=etienne.carriere@st.com \
--cc=gabriel.fernandez@foss.st.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=mturquette@baylibre.com \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.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;
as well as URLs for NNTP newsgroup(s).