From: Rob Herring <robh@kernel.org>
To: Eddie James <eajames@linux.ibm.com>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-aspeed@lists.ozlabs.org, andrew@aj.id.au, joel@jms.id.au,
mark.rutland@arm.com, robh+dt@kernel.org, maz@kernel.org,
jason@lakedaemon.net, tglx@linutronix.de,
Eddie James <eajames@linux.ibm.com>
Subject: Re: [PATCH v2 1/4] dt-bindings: interrupt-controller: Add Aspeed SCU interrupt controller
Date: Fri, 11 Oct 2019 09:33:48 -0500 [thread overview]
Message-ID: <20191011143348.GA22630@bogus> (raw)
In-Reply-To: <1569617929-29055-2-git-send-email-eajames@linux.ibm.com>
On Fri, 27 Sep 2019 15:58:46 -0500, Eddie James wrote:
> Document the Aspeed SCU interrupt controller and add an include file
> for the interrupts it provides.
>
> Signed-off-by: Eddie James <eajames@linux.ibm.com>
> ---
> .../interrupt-controller/aspeed,ast2xxx-scu-ic.txt | 26 ++++++++++++++++++++++
> MAINTAINERS | 7 ++++++
> .../interrupt-controller/aspeed-scu-ic.h | 23 +++++++++++++++++++
> 3 files changed, 56 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/interrupt-controller/aspeed,ast2xxx-scu-ic.txt
> create mode 100644 include/dt-bindings/interrupt-controller/aspeed-scu-ic.h
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2019-10-11 14:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-27 20:58 [PATCH v2 0/4] irqchip: Add Aspeed SCU Interrupt Controller Eddie James
2019-09-27 20:58 ` [PATCH v2 1/4] dt-bindings: interrupt-controller: Add Aspeed SCU interrupt controller Eddie James
2019-10-11 14:33 ` Rob Herring [this message]
2019-09-27 20:58 ` [PATCH v2 2/4] irqchip: " Eddie James
2019-12-03 1:49 ` Andrew Jeffery
2019-09-27 20:58 ` [PATCH v2 3/4] ARM: dts: aspeed: ast2500: Add " Eddie James
2019-09-27 20:58 ` [PATCH v2 4/4] ARM: dts: aspeed: ast2600: Add SCU interrupt controllers Eddie James
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=20191011143348.GA22630@bogus \
--to=robh@kernel.org \
--cc=andrew@aj.id.au \
--cc=devicetree@vger.kernel.org \
--cc=eajames@linux.ibm.com \
--cc=jason@lakedaemon.net \
--cc=joel@jms.id.au \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--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).