From: Marc Zyngier <maz@kernel.org>
To: Nicolas Frayer <nfrayer@baylibre.com>
Cc: tglx@linutronix.de, linux-kernel@vger.kernel.org,
khilman@baylibre.com, glaroque@baylibre.com
Subject: Re: [PATCH 0/2] irqchip: Kconfig: Add module support for TI inta/intr
Date: Wed, 16 Nov 2022 21:44:22 +0000 [thread overview]
Message-ID: <864juypoax.wl-maz@kernel.org> (raw)
In-Reply-To: <20221116185500.40431-1-nfrayer@baylibre.com>
On Wed, 16 Nov 2022 18:54:58 +0000,
Nicolas Frayer <nfrayer@baylibre.com> wrote:
>
> Added module support for TI interrupt aggregator and interrupt router
>
> Nicolas Frayer (2):
> irqchip: Kconfig: module build support for the TI interrupt router
> driver
> irqchip: Kconfig: Added module build support for the TI interrupt
> aggregator
>
> arch/arm64/Kconfig.platforms | 2 --
> drivers/irqchip/Kconfig | 12 +++++++-----
> 2 files changed, 7 insertions(+), 7 deletions(-)
How did you test that it doesn't introduce any regression due to
implicit ordering requirements that are now voided?
Please Cc the TI folks so that they can at least check this.
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2022-11-16 21:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 18:54 [PATCH 0/2] irqchip: Kconfig: Add module support for TI inta/intr Nicolas Frayer
2022-11-16 18:54 ` [PATCH 1/2] irqchip: Kconfig: module build support for the TI interrupt router driver Nicolas Frayer
2022-11-26 22:03 ` kernel test robot
2022-11-16 18:55 ` [PATCH 2/2] irqchip: Kconfig: Added module build support for the TI interrupt aggregator Nicolas Frayer
2022-11-17 16:57 ` kernel test robot
2022-11-16 21:44 ` Marc Zyngier [this message]
2022-11-17 20:49 ` [PATCH 0/2] irqchip: Kconfig: Add module support for TI inta/intr Nicolas Frayer
2022-11-17 21:00 ` 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=864juypoax.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=glaroque@baylibre.com \
--cc=khilman@baylibre.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nfrayer@baylibre.com \
--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