All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gregory CLEMENT <gregory.clement@bootlin.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
	"Thomas Gleixner" <tglx@linutronix.de>
Cc: Andrew Lunn <andrew@lunn.ch>,
	Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, kernel@pengutronix.de
Subject: Re: [PATCH 07/13] irqchip/mvebu-pic: Convert to platform remove callback returning void
Date: Tue, 27 Feb 2024 17:44:04 +0100	[thread overview]
Message-ID: <87r0gxj1rf.fsf@BL-laptop> (raw)
In-Reply-To: <df977ad4c02ff913b01cdd6c348e7fae3e08e651.1703284359.git.u.kleine-koenig@pengutronix.de>

Uwe Kleine-König <u.kleine-koenig@pengutronix.de> writes:

> 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>

Acked-by: Gregory CLEMENT <gregory.clement@bootlin.com>

Thanks,

Gregory
> ---
>  drivers/irqchip/irq-mvebu-pic.c | 6 ++----
>  1 file changed, 2 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/irqchip/irq-mvebu-pic.c b/drivers/irqchip/irq-mvebu-pic.c
> index ef3d3646ccc2..57e3f99b61f5 100644
> --- a/drivers/irqchip/irq-mvebu-pic.c
> +++ b/drivers/irqchip/irq-mvebu-pic.c
> @@ -167,14 +167,12 @@ static int mvebu_pic_probe(struct platform_device *pdev)
>  	return 0;
>  }
>  
> -static int mvebu_pic_remove(struct platform_device *pdev)
> +static void mvebu_pic_remove(struct platform_device *pdev)
>  {
>  	struct mvebu_pic *pic = platform_get_drvdata(pdev);
>  
>  	on_each_cpu(mvebu_pic_disable_percpu_irq, pic, 1);
>  	irq_domain_remove(pic->domain);
> -
> -	return 0;
>  }
>  
>  static const struct of_device_id mvebu_pic_of_match[] = {
> @@ -185,7 +183,7 @@ MODULE_DEVICE_TABLE(of, mvebu_pic_of_match);
>  
>  static struct platform_driver mvebu_pic_driver = {
>  	.probe  = mvebu_pic_probe,
> -	.remove = mvebu_pic_remove,
> +	.remove_new = mvebu_pic_remove,
>  	.driver = {
>  		.name = "mvebu-pic",
>  		.of_match_table = mvebu_pic_of_match,
> -- 
> 2.42.0
>

-- 
Gregory Clement, Bootlin
Embedded Linux and Kernel engineering
http://bootlin.com

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: Gregory CLEMENT <gregory.clement@bootlin.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
	"Thomas Gleixner" <tglx@linutronix.de>
Cc: Andrew Lunn <andrew@lunn.ch>,
	Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, kernel@pengutronix.de
Subject: Re: [PATCH 07/13] irqchip/mvebu-pic: Convert to platform remove callback returning void
Date: Tue, 27 Feb 2024 17:44:04 +0100	[thread overview]
Message-ID: <87r0gxj1rf.fsf@BL-laptop> (raw)
In-Reply-To: <df977ad4c02ff913b01cdd6c348e7fae3e08e651.1703284359.git.u.kleine-koenig@pengutronix.de>

Uwe Kleine-König <u.kleine-koenig@pengutronix.de> writes:

> 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>

Acked-by: Gregory CLEMENT <gregory.clement@bootlin.com>

Thanks,

Gregory
> ---
>  drivers/irqchip/irq-mvebu-pic.c | 6 ++----
>  1 file changed, 2 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/irqchip/irq-mvebu-pic.c b/drivers/irqchip/irq-mvebu-pic.c
> index ef3d3646ccc2..57e3f99b61f5 100644
> --- a/drivers/irqchip/irq-mvebu-pic.c
> +++ b/drivers/irqchip/irq-mvebu-pic.c
> @@ -167,14 +167,12 @@ static int mvebu_pic_probe(struct platform_device *pdev)
>  	return 0;
>  }
>  
> -static int mvebu_pic_remove(struct platform_device *pdev)
> +static void mvebu_pic_remove(struct platform_device *pdev)
>  {
>  	struct mvebu_pic *pic = platform_get_drvdata(pdev);
>  
>  	on_each_cpu(mvebu_pic_disable_percpu_irq, pic, 1);
>  	irq_domain_remove(pic->domain);
> -
> -	return 0;
>  }
>  
>  static const struct of_device_id mvebu_pic_of_match[] = {
> @@ -185,7 +183,7 @@ MODULE_DEVICE_TABLE(of, mvebu_pic_of_match);
>  
>  static struct platform_driver mvebu_pic_driver = {
>  	.probe  = mvebu_pic_probe,
> -	.remove = mvebu_pic_remove,
> +	.remove_new = mvebu_pic_remove,
>  	.driver = {
>  		.name = "mvebu-pic",
>  		.of_match_table = mvebu_pic_of_match,
> -- 
> 2.42.0
>

-- 
Gregory Clement, Bootlin
Embedded Linux and Kernel engineering
http://bootlin.com

  reply	other threads:[~2024-02-27 16:44 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 [this message]
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
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=87r0gxj1rf.fsf@BL-laptop \
    --to=gregory.clement@bootlin.com \
    --cc=andrew@lunn.ch \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sebastian.hesselbarth@gmail.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 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.