From: Rob Herring <robh@kernel.org>
To: daire.mcnamara@microchip.com
Cc: sboyd@kernel.org, robh+dt@kernel.org, linux-clk@vger.kernel.org,
mturquette@baylibre.com, devicetree@vger.kernel.org,
david.abdurachmanov@gmail.com, padmarao.begari@microchip.com
Subject: Re: [PATCH v1 1/2] dt-bindings: CLK: microchip: Add Microchip PolarFire host binding
Date: Fri, 16 Oct 2020 11:07:59 -0500 [thread overview]
Message-ID: <20201016160759.GB1499240@bogus> (raw)
In-Reply-To: <20201015114725.23137-2-daire.mcnamara@microchip.com>
On Thu, 15 Oct 2020 12:47:24 +0100, daire.mcnamara@microchip.com wrote:
> From: Daire McNamara <daire.mcnamara@microchip.com>
>
> Add device tree bindings for the Microchip PolarFire system
> clock controller
>
> Signed-off-by: Daire McNamara <daire.mcnamara@microchip.com>
> ---
> .../bindings/clock/microchip,pfsoc.yaml | 70 +++++++++++++++++++
> 1 file changed, 70 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/clock/microchip,pfsoc.yaml
>
My bot found errors running 'make dt_binding_check' on your patch:
./Documentation/devicetree/bindings/clock/microchip,pfsoc.yaml:58:111: [warning] line too long (306 > 110 characters) (line-length)
See https://patchwork.ozlabs.org/patch/1382572
If you already ran 'make dt_binding_check' and didn't see the above
error(s), then make sure dt-schema is up to date:
pip3 install git+https://github.com/devicetree-org/dt-schema.git@master --upgrade
Please check and re-submit.
next prev parent reply other threads:[~2020-10-16 16:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 11:47 [PATCH v1 0/2] CLK: microchip: Add clkcfg driver for Microchip PolarFire SoC daire.mcnamara
2020-10-15 11:47 ` [PATCH v1 1/2] dt-bindings: CLK: microchip: Add Microchip PolarFire host binding daire.mcnamara
2020-10-15 12:40 ` Krzysztof Kozlowski
2020-10-16 16:07 ` Rob Herring [this message]
2020-10-15 11:47 ` [PATCH v1 2/2] CLK: microchip: Add driver for Microchip PolarFire SoC daire.mcnamara
2020-10-15 12:52 ` Krzysztof Kozlowski
2020-10-20 0:16 ` 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=20201016160759.GB1499240@bogus \
--to=robh@kernel.org \
--cc=daire.mcnamara@microchip.com \
--cc=david.abdurachmanov@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=padmarao.begari@microchip.com \
--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).