From: Richard Fitzgerald <rf@opensource.cirrus.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Thomas Gleixner" <tglx@linutronix.de>
Cc: Charles Keepax <ckeepax@opensource.cirrus.com>,
<alsa-devel@alsa-project.org>, <patches@opensource.cirrus.com>,
<linux-kernel@vger.kernel.org>, <kernel@pengutronix.de>
Subject: Re: [PATCH 06/13] irqchip/madera: Convert to platform remove callback returning void
Date: Thu, 4 Jan 2024 11:56:11 +0000 [thread overview]
Message-ID: <d6ffe1ae-6561-43a2-a1bc-55c44a6731bd@opensource.cirrus.com> (raw)
In-Reply-To: <64c2f79760c53f29651e7126418c407ff699317d.1703284359.git.u.kleine-koenig@pengutronix.de>
On 22/12/23 22:50, Uwe Kleine-König wrote:
> The .remove() callback for a platform driver returns an int which makes
> many driver authors wrongly assume it's possible to do error handling by
> returning an error code. However the value returned is ignored (apart
> from emitting a warning) and this typically results in resource leaks.
>
> To improve here there is a quest to make the remove callback return
> void. In the first step of this quest all drivers are converted to
> .remove_new(), which already returns void. Eventually after all drivers
> are converted, .remove_new() will be renamed to .remove().
>
> Trivially convert this driver from always returning zero in the remove
> callback to the void returning variant.
>
> Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> ---
> drivers/irqchip/irq-madera.c | 6 ++----
> 1 file changed, 2 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/irqchip/irq-madera.c b/drivers/irqchip/irq-madera.c
> index 3eb1f8cdf674..b424c0a327f7 100644
> --- a/drivers/irqchip/irq-madera.c
> +++ b/drivers/irqchip/irq-madera.c
> @@ -222,7 +222,7 @@ static int madera_irq_probe(struct platform_device *pdev)
> return 0;
> }
>
> -static int madera_irq_remove(struct platform_device *pdev)
> +static void madera_irq_remove(struct platform_device *pdev)
> {
> struct madera *madera = dev_get_drvdata(pdev->dev.parent);
>
> @@ -232,13 +232,11 @@ static int madera_irq_remove(struct platform_device *pdev)
> */
> madera->irq_dev = NULL;
> regmap_del_irq_chip(madera->irq, madera->irq_data);
> -
> - return 0;
> }
>
> static struct platform_driver madera_irq_driver = {
> .probe = &madera_irq_probe,
> - .remove = &madera_irq_remove,
> + .remove_new = madera_irq_remove,
> .driver = {
> .name = "madera-irq",
> .pm = &madera_irq_pm_ops,
Reviewed-by: Richard Fitzgerald <rf@opensource.cirrus.com>
next prev parent reply other threads:[~2024-01-04 12:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-22 22:50 [PATCH 00/13] irqchip: " 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 ` [PATCH 03/13] irqchip/imx-irqsteer: " 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 [this message]
2023-12-22 22:50 ` [PATCH 07/13] irqchip/mvebu-pic: " Uwe Kleine-König
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-24 11:59 ` [Linux-stm32] " 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-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=d6ffe1ae-6561-43a2-a1bc-55c44a6731bd@opensource.cirrus.com \
--to=rf@opensource.cirrus.com \
--cc=alsa-devel@alsa-project.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=tglx@linutronix.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®