From: Rob Herring <robh@kernel.org>
To: "Álvaro Fernández Rojas" <noltari@gmail.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Jonas Gorski <jonas.gorski@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
linux-mips@vger.kernel.org, devicetree@vger.kernel.org,
Marc Zyngier <maz@kernel.org>,
bcm-kernel-feedback-list@broadcom.com,
linux-kernel@vger.kernel.org,
Florian Fainelli <f.fainelli@gmail.com>
Subject: Re: [PATCH v2 1/2] dt-bindings: interrupt-controller: document BCM6345 external interrupt controller
Date: Tue, 23 Feb 2021 21:49:02 -0600 [thread overview]
Message-ID: <1614138542.295948.735514.nullmailer@robh.at.kernel.org> (raw)
In-Reply-To: <20210223204340.312-2-noltari@gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1575 bytes --]
On Tue, 23 Feb 2021 21:43:39 +0100, Álvaro Fernández Rojas wrote:
> Document the binding for the BCM6345 external interrupt controller.
>
> Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
> Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
> ---
> v2: fix title typo.
>
> .../brcm,bcm6345-ext-intc.yaml | 61 +++++++++++++++++++
> 1 file changed, 61 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/interrupt-controller/brcm,bcm6345-ext-intc.yaml
>
My bot found errors running 'make dt_binding_check' on your patch:
yamllint warnings/errors:
dtschema/dtc warnings/errors:
/builds/robherring/linux-dt-review/Documentation/devicetree/bindings/interrupt-controller/brcm,bcm6345-ext-intc.yaml: properties:interrupt-parent: False schema does not allow {'description': 'Specifies the phandle to the parent interrupt controller this one is cascaded from.'}
/builds/robherring/linux-dt-review/Documentation/devicetree/bindings/interrupt-controller/brcm,bcm6345-ext-intc.yaml: ignoring, error in schema: properties: interrupt-parent
warning: no schema found in file: ./Documentation/devicetree/bindings/interrupt-controller/brcm,bcm6345-ext-intc.yaml
See https://patchwork.ozlabs.org/patch/1443622
This check can fail if there are any dependencies. The base for a patch
series is generally the most recent rc1.
If you already ran 'make dt_binding_check' and didn't see the above
error(s), then make sure 'yamllint' is installed and dt-schema is up to
date:
pip3 install dtschema --upgrade
Please check and re-submit.
next prev parent reply other threads:[~2021-02-24 3:49 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-23 18:08 [PATCH 0/2] irqchip: add support for BCM6345 interrupt controller Álvaro Fernández Rojas
2021-02-23 18:08 ` [PATCH 1/2] dt-bindings: interrupt-controller: document BCM6345 external " Álvaro Fernández Rojas
2021-02-23 19:34 ` Rob Herring
2021-02-24 9:35 ` kernel test robot
2021-02-23 18:08 ` [PATCH 2/2] irqchip: add support for BCM6345 " Álvaro Fernández Rojas
2021-02-24 1:38 ` kernel test robot
2021-02-23 20:43 ` [PATCH v2 0/2] " Álvaro Fernández Rojas
2021-02-23 20:43 ` [PATCH v2 1/2] dt-bindings: interrupt-controller: document BCM6345 external " Álvaro Fernández Rojas
2021-02-24 3:39 ` Florian Fainelli
2021-02-24 3:49 ` Rob Herring [this message]
2021-02-23 20:43 ` [PATCH v2 2/2] irqchip: add support for " Álvaro Fernández Rojas
2021-02-24 3:43 ` Florian Fainelli
2021-02-24 7:08 ` Álvaro Fernández Rojas
2021-02-24 7:56 ` [PATCH v2 0/2] irqchip: add support for BCM6345 " Álvaro Fernández Rojas
2021-02-24 7:56 ` [PATCH v2 1/2] dt-bindings: interrupt-controller: document BCM6345 external " Álvaro Fernández Rojas
2021-03-06 20:14 ` Rob Herring
2021-03-07 10:12 ` Álvaro Fernández Rojas
2021-03-10 17:21 ` Rob Herring
2021-02-24 7:56 ` [PATCH v2 2/2] irqchip: add support for " Álvaro Fernández Rojas
2021-03-09 10:58 ` Marc Zyngier
2021-02-24 7:58 ` [PATCH v2 0/2] irqchip: add support for BCM6345 " Álvaro Fernández Rojas
2021-02-24 10:03 ` Marc Zyngier
2021-02-27 6:49 ` Álvaro Fernández Rojas
2021-03-06 20:11 ` 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=1614138542.295948.735514.nullmailer@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=jonas.gorski@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=maz@kernel.org \
--cc=noltari@gmail.com \
--cc=robh+dt@kernel.org \
--cc=tglx@linutronix.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).