From: Thomas Gleixner <tglx@linutronix.de>
To: Guillaume La Roque <glaroque@baylibre.com>, Nishanth Menon <nm@ti.com>
Cc: vigneshr@ti.com, Santosh Shilimkar <ssantosh@kernel.org>,
Tero Kristo <kristo@kernel.org>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 2/2] soc: ti: ti_sci_inta_msi: Enable module compilation support
Date: Wed, 10 Sep 2025 22:23:04 +0200 [thread overview]
Message-ID: <87ldmmrr9z.ffs@tglx> (raw)
In-Reply-To: <0bc124c7-55af-4a25-b02d-3bd9aabf0266@baylibre.com>
On Tue, Sep 02 2025 at 16:40, Guillaume La Roque wrote:
Can you please trim your replies?
> I will resend weries because something look not ok i don't find serie in
> lore or patchwork.
>> If Thomas doesn't mind picking the full series,
Is this actually addressing my previous feedback on this?
https://lore.kernel.org/all/87cy87zx87.ffs@tglx
>>> config TI_SCI_INTA_MSI_DOMAIN
>>> - bool
>>> + tristate "TI SCI INTA MSI Domain driver"
>>> select GENERIC_MSI_IRQ
>>> help
>>> Driver to enable Interrupt Aggregator specific MSI Domain.
>>> +
>>> + Say Y here to compile it into the kernel or M to compile it as a
>>> + module. The module will be called ti_sci_inta_msi.
I doubt it, otherwise this would not exist anymore.
If you disagree with me, then have the courtesy to tell me why. Just
ignoring me is not an option.
Thanks
tglx
prev parent reply other threads:[~2025-09-10 20:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250812-timsi-v2-0-90c8500f3f18@baylibre.com>
[not found] ` <20250812-timsi-v2-2-90c8500f3f18@baylibre.com>
2025-08-13 15:26 ` [PATCH v2 2/2] soc: ti: ti_sci_inta_msi: Enable module compilation support Nishanth Menon
2025-09-02 14:40 ` Guillaume La Roque
2025-09-10 20:23 ` Thomas Gleixner [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=87ldmmrr9z.ffs@tglx \
--to=tglx@linutronix.de \
--cc=glaroque@baylibre.com \
--cc=kristo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=ssantosh@kernel.org \
--cc=vigneshr@ti.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