From: Thomas Gleixner <tglx@kernel.org>
To: Frank Li <Frank.li@oss.nxp.com>, Zhipeng.wang_1@oss.nxp.com
Cc: Marc Zyngier <maz@kernel.org>, Frank Li <Frank.Li@nxp.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
Jindong Yue <jindong.yue@nxp.com>,
xuegang.liu@nxp.com, linux-kernel@vger.kernel.org,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4 2/5] irqchip/imx-irqsteer: Use devm to manage the IRQ domain
Date: Wed, 19 Aug 2026 18:28:09 +0200 [thread overview]
Message-ID: <87tsoqjcrq.ffs@fw13> (raw)
In-Reply-To: <aoW8tbTmjMKs1IEO@SMW015318>
On Wed, Aug 19 2026 at 09:24, Frank Li wrote:
>> Fixes: 28528fca4908 ("irqchip/imx-irqsteer: Add multi output interrupts support")
>
> Nit: First patch also need fixes tags to backport.
No. That first patch is not fixing anything and I just explained how
this is done.
next prev parent reply other threads:[~2026-08-19 16:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 9:05 [PATCH v4 0/5] irqchip/imx-irqsteer: Allow building as module Zhipeng.wang_1
2026-08-19 9:05 ` [PATCH v4 1/5] genirq/irqdomain: Add devm_irq_domain_create_linear() Zhipeng.wang_1
2026-08-19 14:23 ` Frank Li
2026-08-19 16:27 ` Thomas Gleixner
2026-08-19 9:05 ` [PATCH v4 2/5] irqchip/imx-irqsteer: Use devm to manage the IRQ domain Zhipeng.wang_1
2026-08-19 14:24 ` Frank Li
2026-08-19 16:28 ` Thomas Gleixner [this message]
2026-08-19 9:05 ` [PATCH v4 3/5] irqchip/imx-irqsteer: Dispose of parent IRQ mappings in remove() Zhipeng.wang_1
2026-08-19 9:18 ` sashiko-bot
2026-08-19 14:25 ` Frank Li
2026-08-19 9:05 ` [PATCH v4 4/5] irqchip/imx-irqsteer: Mask all interrupts in probe() Zhipeng.wang_1
2026-08-19 9:25 ` sashiko-bot
2026-08-19 14:40 ` Frank Li
2026-08-19 15:02 ` Fabio Estevam
2026-08-19 16:30 ` Frank Li
2026-08-19 16:37 ` Fabio Estevam
2026-08-19 9:05 ` [PATCH v4 5/5] irqchip/imx-irqsteer: Allow building as module Zhipeng.wang_1
2026-08-19 9:24 ` sashiko-bot
2026-08-19 15:17 ` Frank Li
2026-08-19 16:30 ` Thomas Gleixner
2026-08-19 16:20 ` [PATCH v4 0/5] " Thomas Gleixner
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=87tsoqjcrq.ffs@fw13 \
--to=tglx@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=Frank.li@oss.nxp.com \
--cc=Zhipeng.wang_1@oss.nxp.com \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=jindong.yue@nxp.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=xuegang.liu@nxp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.