From: Marc Zyngier <maz@kernel.org>
To: Mathias Kresin <dev@kresin.me>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
Serge Semin <fancer.lancer@gmail.com>, Suman Anna <s-anna@ti.com>
Cc: Hauke Mehrtens <hauke@hauke-m.de>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
stable@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Grzegorz Jaszczyk <grzegorz.jaszczyk@linaro.org>,
Lokesh Vutla <lokeshvutla@ti.com>,
linux-omap@vger.kernel.org, Tony Lindgren <tony@atomide.com>,
Santosh Shilimkar <ssantosh@kernel.org>,
David Lechner <david@lechnology.com>
Subject: Re: [PATCH] irqchip: Simplify the TI_PRUSS_INTC Kconfig
Date: Sun, 10 Jan 2021 10:24:15 +0000 [thread overview]
Message-ID: <161027422717.65915.12337837723270334988.b4-ty@kernel.org> (raw)
In-Reply-To: <20210108162901.6003-1-s-anna@ti.com>
On Fri, 8 Jan 2021 10:29:01 -0600, Suman Anna wrote:
> The TI PRUSS INTC irqchip driver handles the local interrupt controller
> which is a child device of it's parent PRUSS/ICSSG device. The driver
> was upstreamed in parallel with the PRUSS platform driver, and was
> configurable independently previously. The PRUSS interrupt controller
> is an integral part of the overall PRUSS software architecture, and is
> not useful at all by itself.
>
> [...]
Applied to irq/irqchip-next, thanks!
[1/1] irqchip: Simplify the TI_PRUSS_INTC Kconfig
commit: b8e594fa20d2e33d40c7a8c7c106549a35c38972
Cheers,
M.
--
Without deviation from the norm, progress is not possible.
prev parent reply other threads:[~2021-01-10 10:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-08 16:29 [PATCH] irqchip: Simplify the TI_PRUSS_INTC Kconfig Suman Anna
2021-01-08 23:34 ` David Lechner
2021-01-10 10:24 ` Marc Zyngier [this message]
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=161027422717.65915.12337837723270334988.b4-ty@kernel.org \
--to=maz@kernel.org \
--cc=david@lechnology.com \
--cc=dev@kresin.me \
--cc=fancer.lancer@gmail.com \
--cc=grzegorz.jaszczyk@linaro.org \
--cc=hauke@hauke-m.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=lokeshvutla@ti.com \
--cc=martin.blumenstingl@googlemail.com \
--cc=s-anna@ti.com \
--cc=ssantosh@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=tony@atomide.com \
--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