From: Marc Zyngier <maz@kernel.org>
To: Nishanth Menon <nm@ti.com>
Cc: Guillaume La Roque <glaroque@baylibre.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Tero Kristo <kristo@kernel.org>,
Santosh Shilimkar <ssantosh@kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <vishalm@ti.com>,
Mattijs Korpershoek <mkorpershoek@baylibre.com>,
Kevin Hilman <khilman@baylibre.com>,
Nicolas Frayer <nfrayer@baylibre.com>
Subject: Re: [PATCH v4 0/2] irqchip: Kconfig: Add module support for TI inta/intr
Date: Thu, 02 Jan 2025 13:09:45 +0000 [thread overview]
Message-ID: <86cyh5pdk6.wl-maz@kernel.org> (raw)
In-Reply-To: <20250102124413.wwbfzomjzedbqges@thinness>
On Thu, 02 Jan 2025 12:44:13 +0000,
Nishanth Menon <nm@ti.com> wrote:
>
> On 20:36-20241224, Guillaume La Roque wrote:
> > Added module support for TI interrupt aggregator and interrupt router
> > drivers. Default value for both drivers is ARCH_K3 and the interrupt
> > aggregator depends on ARCH_K3 as it contains 64 bit only ops.
> > Tested allmodconfig builds with ARCH=arm and ARCH=arm64.
> >
> > Changes in v4:
> > - Rework commit message and title
> > - Add depends on in Kconfig frivers
> > - Link to v3: https://lore.kernel.org/r/20241016-timodules-v3-0-fa71091ade98@baylibre.com
> >
> > Changes in v3:
> > - Add MODULE_LICENSE in drivers
> >
> > Changes in v2:
> > - Added depends on ARCH_K3 for the interrupt aggregator driver as it
> > uses
> > 64 bit ops
> >
> > Signed-off-by: Guillaume La Roque <glaroque@baylibre.com>
> > ---
> > Nicolas Frayer (2):
> > irqchip/ti-sci-intr: add module build support
> > irqchip/ti-sci-inta : Add module build support
> >
> > arch/arm64/Kconfig.platforms | 2 --
> > drivers/irqchip/Kconfig | 6 ++++--
> > drivers/irqchip/irq-ti-sci-inta.c | 1 +
> > drivers/irqchip/irq-ti-sci-intr.c | 1 +
> > 4 files changed, 6 insertions(+), 4 deletions(-)
> > ---
> > base-commit: 8faabc041a001140564f718dabe37753e88b37fa
> > change-id: 20241016-timodules-174770215dd8
> >
> > Best regards,
> > --
> > Guillaume La Roque <glaroque@baylibre.com>
> >
>
> Reviewed-by: Nishanth Menon <nm@ti.com>
>
> Marc, Can this go via your tree?
I'm only looking after the ARM GICs these days, and not anything else.
Hopefully Thomas will look into it.
THanks,
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2025-01-02 13:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-24 19:36 [PATCH v4 0/2] irqchip: Kconfig: Add module support for TI inta/intr Guillaume La Roque
2024-12-24 19:36 ` [PATCH v4 1/2] irqchip/ti-sci-intr: add module build support Guillaume La Roque
2025-01-15 9:16 ` [tip: irq/core] irqchip/ti-sci-intr: Add " tip-bot2 for Nicolas Frayer
2024-12-24 19:36 ` [PATCH v4 2/2] irqchip/ti-sci-inta : " Guillaume La Roque
2025-01-15 9:16 ` [tip: irq/core] " tip-bot2 for Nicolas Frayer
2025-01-02 12:44 ` [PATCH v4 0/2] irqchip: Kconfig: Add module support for TI inta/intr Nishanth Menon
2025-01-02 13:09 ` Marc Zyngier [this message]
2025-01-02 13:26 ` Nishanth Menon
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=86cyh5pdk6.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=glaroque@baylibre.com \
--cc=khilman@baylibre.com \
--cc=kristo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkorpershoek@baylibre.com \
--cc=nfrayer@baylibre.com \
--cc=nm@ti.com \
--cc=ssantosh@kernel.org \
--cc=tglx@linutronix.de \
--cc=vishalm@ti.com \
--cc=will@kernel.org \
/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