From: Marc Zyngier <marc.zyngier@arm.com>
To: Lokesh Vutla <lokeshvutla@ti.com>
Cc: Santosh Shilimkar <ssantosh@kernel.org>,
Rob Herring <robh+dt@kernel.org>, Nishanth Menon <nm@ti.com>,
<tglx@linutronix.de>, <jason@lakedaemon.net>,
Linux ARM Mailing List <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, Tero Kristo <t-kristo@ti.com>,
Sekhar Nori <nsekhar@ti.com>, Tony Lindgren <tony@atomide.com>,
<linus.walleij@linaro.org>,
Peter Ujfalusi <peter.ujfalusi@ti.com>,
Grygorii Strashko <grygorii.strashko@ti.com>,
Device Tree Mailing List <devicetree@vger.kernel.org>
Subject: Re: [PATCH v8 00/14] Add support for TISCI Interrupt controller drivers
Date: Wed, 01 May 2019 14:45:00 +0100 [thread overview]
Message-ID: <86pnp29tlv.wl-marc.zyngier@arm.com> (raw)
In-Reply-To: <7edd8582-ce51-60a0-24e1-c45fe6725705@ti.com>
On Wed, 01 May 2019 14:23:41 +0100,
Lokesh Vutla <lokeshvutla@ti.com> wrote:
>
> Hi Marc,
[...]
> > Lokesh,
> >
> > Thanks for having respun this quickly.
> >
> > I've applied the first 13 patches to irqchip-next (after tidying up some
> > of the commit messages). I've left the last patch for armsoc to take,
> > unless you guys insist on me taking it.
>
> I prefer if everything goes as a single bundle, unless arm-soc maintainers
> object. Want to start posting DT nodes.
Santosh, Tony: what do you prefer? I don't care either way, but I need
a word from either of you.
>
> >
> > If nothing horrible appears in -next tomorrow, I'll send the 5.2 PR with
> > this series.
>
> Awesome.
>
> >
> > Hopefully we won't see more of this madness any time soon... :-/
>
> IRQCHIP is one part of it. Fun is yet to start with DMA.
Great. Oh well, I guess Robin and Christoph will enjoy the ride!
Thanks,
M.
--
Jazz is not dead, it just smell funny.
next prev parent reply other threads:[~2019-05-01 13:44 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-30 10:12 [PATCH v8 00/14] Add support for TISCI Interrupt controller drivers Lokesh Vutla
2019-04-30 10:12 ` [PATCH v8 01/14] firmware: ti_sci: Add support to get TISCI handle using of_phandle Lokesh Vutla
2019-04-30 10:12 ` [PATCH v8 02/14] firmware: ti_sci: Add support for RM core ops Lokesh Vutla
2019-04-30 10:12 ` [PATCH v8 03/14] firmware: ti_sci: Add support for IRQ management Lokesh Vutla
2019-04-30 10:12 ` [PATCH v8 04/14] firmware: ti_sci: Add RM mapping table for am654 Lokesh Vutla
2019-04-30 10:12 ` [PATCH v8 05/14] firmware: ti_sci: Add helper apis to manage resources Lokesh Vutla
2019-04-30 10:12 ` [PATCH v8 06/14] genirq: Introduce irq_chip_{request,release}_resource_parent() apis Lokesh Vutla
2019-05-16 12:40 ` Linus Walleij
2019-04-30 10:12 ` [PATCH v8 07/14] gpio: thunderx: Use the default parent apis for {request,release}_resources Lokesh Vutla
2020-03-10 23:27 ` Tim Harvey
2020-03-11 4:56 ` Lokesh Vutla
2020-03-11 15:43 ` Thomas Gleixner
2020-03-11 16:09 ` Tim Harvey
2019-04-30 10:12 ` [PATCH v8 08/14] dt-bindings: irqchip: Introduce TISCI Interrupt router bindings Lokesh Vutla
2019-04-30 22:24 ` Rob Herring
2019-04-30 10:12 ` [PATCH v8 09/14] irqchip: ti-sci-intr: Add support for Interrupt Router driver Lokesh Vutla
2019-04-30 10:12 ` [PATCH v8 10/14] dt-bindings: irqchip: Introduce TISCI Interrupt Aggregator bindings Lokesh Vutla
2019-04-30 22:25 ` Rob Herring
2019-04-30 10:12 ` [PATCH v8 11/14] irqchip: ti-sci-inta: Add support for Interrupt Aggregator driver Lokesh Vutla
2019-04-30 10:12 ` [PATCH v8 12/14] soc: ti: Add MSI domain bus support for Interrupt Aggregator Lokesh Vutla
2019-04-30 10:12 ` [PATCH v8 13/14] irqchip: ti-sci-inta: Add msi domain support Lokesh Vutla
2019-04-30 10:12 ` [PATCH v8 14/14] arm64: arch_k3: Enable interrupt controller drivers Lokesh Vutla
2019-04-30 11:45 ` [PATCH v8 00/14] Add support for TISCI Interrupt " Nishanth Menon
2019-05-01 11:58 ` Marc Zyngier
2019-05-01 13:23 ` Lokesh Vutla
2019-05-01 13:45 ` Marc Zyngier [this message]
2019-05-01 14:04 ` Tony Lindgren
2019-05-01 14:31 ` 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=86pnp29tlv.wl-marc.zyngier@arm.com \
--to=marc.zyngier@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=grygorii.strashko@ti.com \
--cc=jason@lakedaemon.net \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lokeshvutla@ti.com \
--cc=nm@ti.com \
--cc=nsekhar@ti.com \
--cc=peter.ujfalusi@ti.com \
--cc=robh+dt@kernel.org \
--cc=ssantosh@kernel.org \
--cc=t-kristo@ti.com \
--cc=tglx@linutronix.de \
--cc=tony@atomide.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).