From: Rob Herring <robh@kernel.org>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: devicetree@vger.kernel.org,
Florian Fainelli <f.fainelli@gmail.com>,
linux-arm-kernel@vger.kernel.org,
open list <linux-kernel@vger.kernel.org>,
"moderated list:BROADCOM BCM2711/BCM2835 ARM ARCHITECTURE"
<linux-rpi-kernel@lists.infradead.org>,
"moderated list:BROADCOM IPROC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 12/12] dt-bindings: arm: bcm: Convert BCM2835 firmware binding to YAML
Date: Mon, 3 Feb 2020 10:14:40 +0000 [thread overview]
Message-ID: <20200203101440.GA31848@bogus> (raw)
In-Reply-To: <20200202211827.27682-13-f.fainelli@gmail.com>
On Sun, 2 Feb 2020 13:18:27 -0800, Florian Fainelli wrote:
> Convert the Raspberry Pi BCM2835 firmware binding document to YAML.
> Verified with dt_binding_check and dtbs_check.
>
> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
> ---
> .../arm/bcm/raspberrypi,bcm2835-firmware.txt | 14 --------
> .../arm/bcm/raspberrypi,bcm2835-firmware.yaml | 33 +++++++++++++++++++
> 2 files changed, 33 insertions(+), 14 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/arm/bcm/raspberrypi,bcm2835-firmware.txt
> create mode 100644 Documentation/devicetree/bindings/arm/bcm/raspberrypi,bcm2835-firmware.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
Documentation/devicetree/bindings/arm/bcm/raspberrypi,bcm2835-firmware.yaml: $id: path/filename 'arm/bcm/raspberrypi,bcm2835.yaml' doesn't match actual filename
Documentation/devicetree/bindings/Makefile:12: recipe for target 'Documentation/devicetree/bindings/arm/bcm/raspberrypi,bcm2835-firmware.example.dts' failed
make[1]: *** [Documentation/devicetree/bindings/arm/bcm/raspberrypi,bcm2835-firmware.example.dts] Error 1
Makefile:1263: recipe for target 'dt_binding_check' failed
make: *** [dt_binding_check] Error 2
See https://patchwork.ozlabs.org/patch/1232487
Please check and re-submit.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2020-02-03 10:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-02 21:18 [PATCH 00/12] dt-bindings: arm: bcm: Convert boards to YAML Florian Fainelli
2020-02-02 21:18 ` [PATCH 01/12] dt-bindings: arm: bcm: Convert Cygnus " Florian Fainelli
2020-02-03 8:29 ` Maxime Ripard
2020-02-02 21:18 ` [PATCH 02/12] dt-bindings: arm: bcm: Convert Hurricane 2 " Florian Fainelli
2020-02-02 21:18 ` [PATCH 03/12] dt-bindings: arm: bcm: Convert Northstar Plus " Florian Fainelli
2020-02-02 21:18 ` [PATCH 04/12] dt-bindings: arm: bcm: Convert Northstar 2 " Florian Fainelli
2020-02-02 21:18 ` [PATCH 05/12] dt-bindings: arm: bcm: Convert Stingray " Florian Fainelli
2020-02-02 21:18 ` [PATCH 06/12] dt-bindings: arm: bcm: Convert BCM21664 " Florian Fainelli
2020-02-03 8:30 ` Maxime Ripard
2020-02-02 21:18 ` [PATCH 07/12] dt-bindings: arm: bcm: Convert BCM23550 " Florian Fainelli
2020-02-02 21:18 ` [PATCH 08/12] dt-bindings: arm: bcm: Convert BCM4708 " Florian Fainelli
2020-02-03 8:31 ` Maxime Ripard
2020-02-02 21:18 ` [PATCH 09/12] dt-bindings: arm: bcm: Convert BCM11351 " Florian Fainelli
2020-02-02 21:18 ` [PATCH 10/12] dt-bindings: arm: bcm: Convert Vulcan " Florian Fainelli
2020-02-02 21:30 ` Rob Herring
2020-02-02 21:18 ` [PATCH 11/12] dt-bindings: arm: Document Broadcom SoCs 'secondary-boot-reg' Florian Fainelli
2020-02-03 8:34 ` Maxime Ripard
2020-02-04 5:29 ` Florian Fainelli
2020-02-04 9:19 ` Maxime Ripard
2020-02-02 21:18 ` [PATCH 12/12] dt-bindings: arm: bcm: Convert BCM2835 firmware binding to YAML Florian Fainelli
2020-02-03 10:14 ` Rob Herring [this message]
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=20200203101440.GA31848@bogus \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-kernel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.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).