From: Rob Herring <robh@kernel.org>
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: Rob Herring <robh+dt@kernel.org>,
linux-kernel@vger.kernel.org, mkl@pengutronix.de,
netdev@vger.kernel.org, kernel@pengutronix.de,
linux-can@vger.kernel.org, Jakub Kicinski <kuba@kernel.org>,
devicetree@vger.kernel.org,
Wolfgang Grandegger <wg@grandegger.com>,
Joakim Zhang <qiangqing.zhang@nxp.com>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH v2 1/2] dt-bindings: can: add can-controller.yaml
Date: Fri, 16 Oct 2020 11:11:26 -0500 [thread overview]
Message-ID: <20201016161126.GA1504381@bogus> (raw)
In-Reply-To: <20201016073315.16232-2-o.rempel@pengutronix.de>
On Fri, 16 Oct 2020 09:33:14 +0200, Oleksij Rempel wrote:
> For now we have only node name as common rule for all CAN controllers
>
> Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
> ---
> .../bindings/net/can/can-controller.yaml | 16 ++++++++++++++++
> 1 file changed, 16 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/net/can/can-controller.yaml
>
My bot found errors running 'make dt_binding_check' on your patch:
./Documentation/devicetree/bindings/net/can/can-controller.yaml: $id: relative path/filename doesn't match actual path or filename
expected: http://devicetree.org/schemas/net/can/can-controller.yaml#
See https://patchwork.ozlabs.org/patch/1383115
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:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-16 7:33 [PATCH v2 0/2] convert flexcan to the yaml Oleksij Rempel
2020-10-16 7:33 ` [PATCH v2 1/2] dt-bindings: can: add can-controller.yaml Oleksij Rempel
2020-10-16 16:11 ` Rob Herring [this message]
2020-10-16 16:13 ` Rob Herring
2020-10-16 7:33 ` [PATCH v2 2/2] dt-bindings: can: flexcan: convert fsl,*flexcan bindings to yaml Oleksij Rempel
2020-10-19 21:25 ` Rob Herring
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=20201016161126.GA1504381@bogus \
--to=robh@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=qiangqing.zhang@nxp.com \
--cc=robh+dt@kernel.org \
--cc=wg@grandegger.com \
/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).