From: Rob Herring <robh@kernel.org>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Jakub Kicinski <kuba@kernel.org>,
Michael Hennerich <michael.hennerich@analog.com>,
Eric Dumazet <edumazet@google.com>,
Josua Mayer <josua@solid-run.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>,
Alexandru Ardelean <alexandru.ardelean@analog.com>,
Paolo Abeni <pabeni@redhat.com>,
linux-kernel@vger.kernel.org,
"David S . Miller" <davem@davemloft.net>
Subject: Re: [PATCH] dt-bindings: net: adin: Fix adi,phy-output-clock description syntax
Date: Wed, 25 May 2022 20:53:47 -0500 [thread overview]
Message-ID: <20220526015347.GA2890726-robh@kernel.org> (raw)
In-Reply-To: <6fcef2665a6cd86a021509a84c5956ec2efd93ed.1653401420.git.geert+renesas@glider.be>
On Tue, 24 May 2022 16:11:53 +0200, Geert Uytterhoeven wrote:
> "make dt_binding_check":
>
> Documentation/devicetree/bindings/net/adi,adin.yaml:40:77: [error] syntax error: mapping values are not allowed here (syntax)
>
> The first line of the description ends with a colon, hence the block
> needs to be marked with a "|".
>
> Fixes: 1f77204e11f8b9e5 ("dt-bindings: net: adin: document phy clock output properties")
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> Documentation/devicetree/bindings/net/adi,adin.yaml | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2022-05-26 1:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-24 14:11 [PATCH] dt-bindings: net: adin: Fix adi,phy-output-clock description syntax Geert Uytterhoeven
2022-05-24 14:30 ` Geert Uytterhoeven
2022-05-24 18:24 ` Jakub Kicinski
2022-05-25 12:28 ` alexandru.tachici
2022-05-25 12:31 ` Geert Uytterhoeven
2022-05-25 5:33 ` Josua Mayer
2022-05-26 1:53 ` Rob Herring [this message]
2022-05-26 5:10 ` patchwork-bot+netdevbpf
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=20220526015347.GA2890726-robh@kernel.org \
--to=robh@kernel.org \
--cc=alexandru.ardelean@analog.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=geert+renesas@glider.be \
--cc=josua@solid-run.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.hennerich@analog.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh+dt@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 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.