mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: <Nicolas.Ferre@microchip.com>
To: <u.kleine-koenig@pengutronix.de>, <arnd@arndb.de>,
	<gregkh@linuxfoundation.org>
Cc: <kernel@pengutronix.de>, <claudiu.beznea@tuxon.dev>,
	<alexandre.belloni@bootlin.com>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 01/11] misc: atmel-ssc: Convert to platform remove callback returning void
Date: Wed, 21 Feb 2024 13:49:18 +0000	[thread overview]
Message-ID: <aa1338c9-0880-45fb-9ba0-9ce2025b1018@microchip.com> (raw)
In-Reply-To: <45719fc31bb893bb9ab1450057e9cb7f399e9ee2.1708508896.git.u.kleine-koenig@pengutronix.de>

On 21/02/2024 at 10:53, 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>

Acked-by: Nicolas Ferre <nicolas.ferre@microchip.com>
Thanks Uwe.

> ---
>   drivers/misc/atmel-ssc.c | 6 ++----
>   1 file changed, 2 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/misc/atmel-ssc.c b/drivers/misc/atmel-ssc.c
> index ee590c4a1537..6eac0f335915 100644
> --- a/drivers/misc/atmel-ssc.c
> +++ b/drivers/misc/atmel-ssc.c
> @@ -251,7 +251,7 @@ static int ssc_probe(struct platform_device *pdev)
>          return 0;
>   }
> 
> -static int ssc_remove(struct platform_device *pdev)
> +static void ssc_remove(struct platform_device *pdev)
>   {
>          struct ssc_device *ssc = platform_get_drvdata(pdev);
> 
> @@ -260,8 +260,6 @@ static int ssc_remove(struct platform_device *pdev)
>          mutex_lock(&user_lock);
>          list_del(&ssc->list);
>          mutex_unlock(&user_lock);
> -
> -       return 0;
>   }
> 
>   static struct platform_driver ssc_driver = {
> @@ -271,7 +269,7 @@ static struct platform_driver ssc_driver = {
>          },
>          .id_table       = atmel_ssc_devtypes,
>          .probe          = ssc_probe,
> -       .remove         = ssc_remove,
> +       .remove_new     = ssc_remove,
>   };
>   module_platform_driver(ssc_driver);
> 
> --
> 2.43.0
> 


  reply	other threads:[~2024-02-21 13:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-21  9:53 [PATCH 00/11] misc: " Uwe Kleine-König
2024-02-21  9:53 ` [PATCH 01/11] misc: atmel-ssc: " Uwe Kleine-König
2024-02-21 13:49   ` Nicolas.Ferre [this message]
2024-02-21  9:53 ` [PATCH 02/11] cxl: " Uwe Kleine-König
2024-02-22  2:46   ` Andrew Donnellan
2024-02-21  9:53 ` [PATCH 03/11] misc: fastrpc: " Uwe Kleine-König
2024-02-21  9:53 ` [PATCH 04/11] misc: hisi_hikey_usb: " Uwe Kleine-König
2024-02-21 19:16   ` John Stultz
2024-02-21  9:53 ` [PATCH 05/11] mei: vsc: " Uwe Kleine-König
2024-02-21  9:53 ` [PATCH 06/11] misc: open-dice: " Uwe Kleine-König
2024-02-21  9:53 ` [PATCH 07/11] misc: sram: " Uwe Kleine-König
2024-02-21  9:53 ` [PATCH 08/11] misc: ti-st: st_kim: " Uwe Kleine-König
2024-02-21  9:53 ` [PATCH 09/11] misc: vcpu_stall_detector: " Uwe Kleine-König
2024-02-21  9:53 ` [PATCH 10/11] misc: xilinx_sdfec: " Uwe Kleine-König
2024-02-21  9:53 ` [PATCH 11/11] misc: xilinx_tmr_inject: " Uwe Kleine-König
2024-02-21 13:52 ` [PATCH 00/11] misc: " Arnd Bergmann
2024-03-04 22:36   ` Uwe Kleine-König
2024-03-04 23:42     ` Greg Kroah-Hartman

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=aa1338c9-0880-45fb-9ba0-9ce2025b1018@microchip.com \
    --to=nicolas.ferre@microchip.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=arnd@arndb.de \
    --cc=claudiu.beznea@tuxon.dev \
    --cc=gregkh@linuxfoundation.org \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.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 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®