From: Rob Herring <robh@kernel.org>
To: Gregory CLEMENT <gregory.clement@bootlin.com>
Cc: linux-kernel@vger.kernel.org,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Rob Herring <robh+dt@kernel.org>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Lars Povlsen <lars.povlsen@microchip.com>,
Steen.Hegelund@microchip.com,
Thomas Gleixner <tglx@linutronix.de>,
devicetree@vger.kernel.org, Marc Zyngier <maz@kernel.org>,
Jason Cooper <jason@lakedaemon.net>
Subject: Re: [PATCH v5 1/6] dt-bindings: interrupt-controller: convert icpu intr bindings to json-schema
Date: Mon, 30 Nov 2020 15:52:16 -0700 [thread overview]
Message-ID: <20201130225216.GA3187386@robh.at.kernel.org> (raw)
In-Reply-To: <20201125103206.136498-2-gregory.clement@bootlin.com>
On Wed, 25 Nov 2020 11:32:01 +0100, Gregory CLEMENT wrote:
> Convert device tree bindings for Microsemi Ocelot SoC ICPU Interrupt
> Controller to YAML format
>
> Signed-off-by: Gregory CLEMENT <gregory.clement@bootlin.com>
> ---
> .../mscc,ocelot-icpu-intr.txt | 21 -------
> .../mscc,ocelot-icpu-intr.yaml | 60 +++++++++++++++++++
> 2 files changed, 60 insertions(+), 21 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/interrupt-controller/mscc,ocelot-icpu-intr.txt
> create mode 100644 Documentation/devicetree/bindings/interrupt-controller/mscc,ocelot-icpu-intr.yaml
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2020-11-30 22:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-25 10:32 [PATCH v5 0/6] Extend irqchip ocelot driver to support other SoCs Gregory CLEMENT
2020-11-25 10:32 ` [PATCH v5 1/6] dt-bindings: interrupt-controller: convert icpu intr bindings to json-schema Gregory CLEMENT
2020-11-30 22:52 ` Rob Herring [this message]
2020-12-11 14:58 ` [irqchip: irq/irqchip-next] " irqchip-bot for Gregory CLEMENT
2020-11-25 10:32 ` [PATCH v5 2/6] dt-bindings: interrupt-controller: Add binding for few Microsemi interrupt controllers Gregory CLEMENT
2020-11-30 22:52 ` Rob Herring
2020-12-11 14:58 ` [irqchip: irq/irqchip-next] " irqchip-bot for Gregory CLEMENT
2020-11-25 10:32 ` [PATCH v5 3/6] irqchip: ocelot: prepare to support more SoC Gregory CLEMENT
2020-12-11 14:58 ` [irqchip: irq/irqchip-next] irqchip/ocelot: " irqchip-bot for Gregory CLEMENT
2020-11-25 10:32 ` [PATCH v5 4/6] irqchip: ocelot: Add support for Luton platforms Gregory CLEMENT
2020-12-11 14:58 ` [irqchip: irq/irqchip-next] irqchip/ocelot: " irqchip-bot for Gregory CLEMENT
2020-11-25 10:32 ` [PATCH v5 5/6] irqchip: ocelot: Add support for Serval platforms Gregory CLEMENT
2020-12-11 14:58 ` [irqchip: irq/irqchip-next] irqchip/ocelot: " irqchip-bot for Gregory CLEMENT
2020-11-25 10:32 ` [PATCH v5 6/6] irqchip: ocelot: Add support for Jaguar2 platforms Gregory CLEMENT
2020-12-11 14:58 ` [irqchip: irq/irqchip-next] irqchip/ocelot: " irqchip-bot for Gregory CLEMENT
2020-12-11 15:01 ` [PATCH v5 0/6] Extend irqchip ocelot driver to support other SoCs Marc Zyngier
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=20201130225216.GA3187386@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=Steen.Hegelund@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=gregory.clement@bootlin.com \
--cc=jason@lakedaemon.net \
--cc=lars.povlsen@microchip.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=robh+dt@kernel.org \
--cc=tglx@linutronix.de \
--cc=thomas.petazzoni@bootlin.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).