From: Rob Herring <robh@kernel.org>
To: "Álvaro Fernández Rojas" <noltari@gmail.com>
Cc: paulburton@kernel.org, tsbogend@alpha.franken.de,
devicetree@vger.kernel.org, kstewart@linuxfoundation.org,
f.fainelli@gmail.com, bcm-kernel-feedback-list@broadcom.com,
lorenzo.pieralisi@arm.com, p.zabel@pengutronix.de,
robh+dt@kernel.org, jonas.gorski@gmail.com,
linux-kernel@vger.kernel.org, info@metux.net, tglx@linutronix.de,
allison@lohutok.net, linux-pci@vger.kernel.org,
jiaxun.yang@flygoat.com, bhelgaas@google.com,
linux-mips@vger.kernel.org
Subject: Re: [PATCH 2/3] dt-bindings: Document BCM6328 PCIe Host Controller
Date: Wed, 17 Jun 2020 11:07:38 -0600 [thread overview]
Message-ID: <20200617170738.GA2315041@bogus> (raw)
In-Reply-To: <20200617102556.3792821-3-noltari@gmail.com>
On Wed, 17 Jun 2020 12:25:55 +0200, Álvaro Fernández Rojas wrote:
> BCM6328 PCIe host controller is found on BCM6328, BCM6362 and BCM63268 SoCs.
>
> Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
> ---
> .../bindings/pci/brcm,bcm6328-pcie.yaml | 109 ++++++++++++++++++
> 1 file changed, 109 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/pci/brcm,bcm6328-pcie.yaml
>
My bot found errors running 'make dt_binding_check' on your patch:
Error: Documentation/devicetree/bindings/pci/brcm,bcm6328-pcie.example.dts:38.49-50 syntax error
FATAL ERROR: Unable to parse input tree
scripts/Makefile.lib:315: recipe for target 'Documentation/devicetree/bindings/pci/brcm,bcm6328-pcie.example.dt.yaml' failed
make[1]: *** [Documentation/devicetree/bindings/pci/brcm,bcm6328-pcie.example.dt.yaml] Error 1
make[1]: *** Waiting for unfinished jobs....
Makefile:1347: recipe for target 'dt_binding_check' failed
make: *** [dt_binding_check] Error 2
See https://patchwork.ozlabs.org/patch/1311090
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-06-17 17:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-17 10:25 [PATCH 0/3] mips: bmips: add BCM6328 PCIe support Álvaro Fernández Rojas
2020-06-17 10:25 ` [PATCH 1/3] mips: bmips: add PCI support Álvaro Fernández Rojas
2020-06-17 11:09 ` Thomas Bogendoerfer
2020-06-17 10:25 ` [PATCH 2/3] dt-bindings: Document BCM6328 PCIe Host Controller Álvaro Fernández Rojas
2020-06-17 17:07 ` Rob Herring [this message]
2020-06-17 21:50 ` Florian Fainelli
2020-06-17 10:25 ` [PATCH 3/3] pci: add BCM6328 PCIe controller support Álvaro Fernández Rojas
2020-06-17 15:50 ` Bjorn Helgaas
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=20200617170738.GA2315041@bogus \
--to=robh@kernel.org \
--cc=allison@lohutok.net \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=info@metux.net \
--cc=jiaxun.yang@flygoat.com \
--cc=jonas.gorski@gmail.com \
--cc=kstewart@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=noltari@gmail.com \
--cc=p.zabel@pengutronix.de \
--cc=paulburton@kernel.org \
--cc=robh+dt@kernel.org \
--cc=tglx@linutronix.de \
--cc=tsbogend@alpha.franken.de \
/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).