From: Thomas Gleixner <tglx@linutronix.de>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Andrew Lunn <andrew@lunn.ch>,
alsa-devel@alsa-project.org,
Charles Keepax <ckeepax@opensource.cirrus.com>,
kernel@pengutronix.de, Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
linux-stm32@st-md-mailman.stormreply.com,
linux-kernel@vger.kernel.org,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Richard Fitzgerald <rf@opensource.cirrus.com>,
NXP Linux Team <linux-imx@nxp.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
patches@opensource.cirrus.com, Fabio Estevam <festevam@gmail.com>,
Gregory Clement <gregory.clement@bootlin.com>,
linux-arm-kernel@lists.infradead.org,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Subject: Re: [PATCH 00/13] irqchip: Convert to platform remove callback returning void
Date: Tue, 27 Feb 2024 18:03:07 +0100 [thread overview]
Message-ID: <874jdtalh0.ffs@tglx> (raw)
In-Reply-To: <knhwqxhouaiehmnnz5oxaxibhq7usokefztae4pplqypwuzgye@mke2irokres4>
On Thu, Feb 15 2024 at 22:03, Uwe Kleine-König wrote:
> On Fri, Dec 22, 2023 at 11:50:31PM +0100, Uwe Kleine-König wrote:
>> this series converts all drivers below drivers/irqchip to use
>> .remove_new(). See commit 5c5a7680e67b ("platform: Provide a remove
>> callback that returns no value") for an extended explanation and the
>> eventual goal. The TL;DR; is to make it harder for driver authors to
>> leak resources.
>>
>> The drivers touched here are all fine though and don't return early in
>> .remove(). So all conversions in this series are trivial.
>
> I'm still waiting for this series to go in (or get review feedback). Is
> this still on your radar? You're the right maintainer to take this
> series, aren't you?
I am and it fell through my christmas crack. I don't even try to catch
up with email after being almost 3 weeks AFK. For two decades I rely on
submitters to ping me after a couple of weeks or month in this case :)
Thanks,
tglx
WARNING: multiple messages have this Message-ID (diff)
From: Thomas Gleixner <tglx@linutronix.de>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Andrew Lunn <andrew@lunn.ch>,
alsa-devel@alsa-project.org,
Charles Keepax <ckeepax@opensource.cirrus.com>,
kernel@pengutronix.de, Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
linux-stm32@st-md-mailman.stormreply.com,
linux-kernel@vger.kernel.org,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Richard Fitzgerald <rf@opensource.cirrus.com>,
NXP Linux Team <linux-imx@nxp.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
patches@opensource.cirrus.com, Fabio Estevam <festevam@gmail.com>,
Gregory Clement <gregory.clement@bootlin.com>,
linux-arm-kernel@lists.infradead.org,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Subject: Re: [PATCH 00/13] irqchip: Convert to platform remove callback returning void
Date: Tue, 27 Feb 2024 18:03:07 +0100 [thread overview]
Message-ID: <874jdtalh0.ffs@tglx> (raw)
In-Reply-To: <knhwqxhouaiehmnnz5oxaxibhq7usokefztae4pplqypwuzgye@mke2irokres4>
On Thu, Feb 15 2024 at 22:03, Uwe Kleine-König wrote:
> On Fri, Dec 22, 2023 at 11:50:31PM +0100, Uwe Kleine-König wrote:
>> this series converts all drivers below drivers/irqchip to use
>> .remove_new(). See commit 5c5a7680e67b ("platform: Provide a remove
>> callback that returns no value") for an extended explanation and the
>> eventual goal. The TL;DR; is to make it harder for driver authors to
>> leak resources.
>>
>> The drivers touched here are all fine though and don't return early in
>> .remove(). So all conversions in this series are trivial.
>
> I'm still waiting for this series to go in (or get review feedback). Is
> this still on your radar? You're the right maintainer to take this
> series, aren't you?
I am and it fell through my christmas crack. I don't even try to catch
up with email after being almost 3 weeks AFK. For two decades I rely on
submitters to ping me after a couple of weeks or month in this case :)
Thanks,
tglx
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-02-27 17:03 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-22 22:50 [PATCH 00/13] irqchip: Convert to platform remove callback returning void Uwe Kleine-König
2023-12-22 22:50 ` Uwe Kleine-König
2023-12-22 22:50 ` [PATCH 01/13] irqchip/imgpdc: " Uwe Kleine-König
2023-12-22 22:50 ` [PATCH 02/13] irqchip/imx-intmux: " Uwe Kleine-König
2023-12-22 22:50 ` Uwe Kleine-König
2023-12-22 22:50 ` [PATCH 03/13] irqchip/imx-irqsteer: " Uwe Kleine-König
2023-12-22 22:50 ` Uwe Kleine-König
2023-12-22 22:50 ` [PATCH 04/13] irqchip/keystone: " Uwe Kleine-König
2023-12-22 22:50 ` [PATCH 05/13] irqchip/ls-scfg-msi: " Uwe Kleine-König
2023-12-22 22:50 ` [PATCH 06/13] irqchip/madera: " Uwe Kleine-König
2024-01-04 11:56 ` Richard Fitzgerald
2023-12-22 22:50 ` [PATCH 07/13] irqchip/mvebu-pic: " Uwe Kleine-König
2023-12-22 22:50 ` Uwe Kleine-König
2024-02-27 16:44 ` Gregory CLEMENT
2024-02-27 16:44 ` Gregory CLEMENT
2023-12-22 22:50 ` [PATCH 08/13] irqchip/pruss-intc: " Uwe Kleine-König
2023-12-22 22:50 ` [PATCH 09/13] irqchip/renesas-intc-irqpin: " Uwe Kleine-König
2023-12-22 22:50 ` [PATCH 10/13] irqchip/renesas-irqc: " Uwe Kleine-König
2023-12-22 22:50 ` [PATCH 11/13] irqchip/renesas-rza1: " Uwe Kleine-König
2023-12-22 22:50 ` [PATCH 12/13] irqchip/stm32-exti: " Uwe Kleine-König
2023-12-22 22:50 ` Uwe Kleine-König
2023-12-24 11:59 ` [Linux-stm32] " Antonio Borneo
2023-12-24 11:59 ` Antonio Borneo
2023-12-22 22:50 ` [PATCH 13/13] irqchip/ts4800: " Uwe Kleine-König
2024-02-15 21:03 ` [PATCH 00/13] irqchip: " Uwe Kleine-König
2024-02-15 21:03 ` Uwe Kleine-König
2024-02-27 17:03 ` Thomas Gleixner [this message]
2024-02-27 17:03 ` 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=874jdtalh0.ffs@tglx \
--to=tglx@linutronix.de \
--cc=alexandre.torgue@foss.st.com \
--cc=alsa-devel@alsa-project.org \
--cc=andrew@lunn.ch \
--cc=ckeepax@opensource.cirrus.com \
--cc=festevam@gmail.com \
--cc=gregory.clement@bootlin.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=patches@opensource.cirrus.com \
--cc=rf@opensource.cirrus.com \
--cc=s.hauer@pengutronix.de \
--cc=sebastian.hesselbarth@gmail.com \
--cc=shawnguo@kernel.org \
--cc=u.kleine-koenig@pengutronix.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 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.