Linux CAN drivers development
 help / color / mirror / Atom feed
From: <Claudiu.Beznea@microchip.com>
To: <u.kleine-koenig@pengutronix.de>, <wg@grandegger.com>,
	<mkl@pengutronix.de>, <davem@davemloft.net>,
	<edumazet@google.com>, <kuba@kernel.org>, <pabeni@redhat.com>,
	<Nicolas.Ferre@microchip.com>, <alexandre.belloni@bootlin.com>
Cc: <linux-can@vger.kernel.org>, <netdev@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>, <kernel@pengutronix.de>
Subject: Re: [PATCH 01/19] can: at91_can: Convert to platform remove callback returning void
Date: Mon, 15 May 2023 06:48:29 +0000	[thread overview]
Message-ID: <6fd7b691-1a60-4ee3-7292-aa401de16aed@microchip.com> (raw)
In-Reply-To: <20230512212725.143824-2-u.kleine-koenig@pengutronix.de>

On 13.05.2023 00:27, Uwe Kleine-König wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> 
> 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() is
> 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>

Reviewed-by: Claudiu Beznea <claudiu.beznea@microchip.com>


> ---
>  drivers/net/can/at91_can.c | 6 ++----
>  1 file changed, 2 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/net/can/at91_can.c b/drivers/net/can/at91_can.c
> index 199cb200f2bd..4621266851ed 100644
> --- a/drivers/net/can/at91_can.c
> +++ b/drivers/net/can/at91_can.c
> @@ -1346,7 +1346,7 @@ static int at91_can_probe(struct platform_device *pdev)
>         return err;
>  }
> 
> -static int at91_can_remove(struct platform_device *pdev)
> +static void at91_can_remove(struct platform_device *pdev)
>  {
>         struct net_device *dev = platform_get_drvdata(pdev);
>         struct at91_priv *priv = netdev_priv(dev);
> @@ -1362,8 +1362,6 @@ static int at91_can_remove(struct platform_device *pdev)
>         clk_put(priv->clk);
> 
>         free_candev(dev);
> -
> -       return 0;
>  }
> 
>  static const struct platform_device_id at91_can_id_table[] = {
> @@ -1381,7 +1379,7 @@ MODULE_DEVICE_TABLE(platform, at91_can_id_table);
> 
>  static struct platform_driver at91_can_driver = {
>         .probe = at91_can_probe,
> -       .remove = at91_can_remove,
> +       .remove_new = at91_can_remove,
>         .driver = {
>                 .name = KBUILD_MODNAME,
>                 .of_match_table = of_match_ptr(at91_can_dt_ids),
> --
> 2.39.2
> 


  reply	other threads:[~2023-05-15  6:48 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-12 21:27 [PATCH net-next 00/19] can: Convert to platform remove callback returning void Uwe Kleine-König
2023-05-12 21:27 ` [PATCH 01/19] can: at91_can: " Uwe Kleine-König
2023-05-15  6:48   ` Claudiu.Beznea [this message]
2023-05-12 21:27 ` [PATCH 02/19] can: bxcan: " Uwe Kleine-König
2023-05-12 21:27 ` [PATCH 03/19] can: c_can: " Uwe Kleine-König
2023-05-12 21:27 ` [PATCH 04/19] can: cc770_isa: " Uwe Kleine-König
2023-05-12 21:27 ` [PATCH 05/19] can: cc770_platform: " Uwe Kleine-König
2023-05-12 21:27 ` [PATCH 06/19] can: ctucanfd: " Uwe Kleine-König
2023-05-14 13:50   ` Pavel Pisa
2023-05-12 21:27 ` [PATCH 07/19] can: flexcan: " Uwe Kleine-König
2023-05-12 21:27 ` [PATCH 08/19] can: grcan: " Uwe Kleine-König
2023-05-12 21:27 ` [PATCH 09/19] can: ifi_canfd: " Uwe Kleine-König
2023-05-12 21:27 ` [PATCH 10/19] can: janz-ican3: " Uwe Kleine-König
2023-05-12 21:27 ` [PATCH 11/19] can: m_can: " Uwe Kleine-König
2023-05-12 21:27 ` [PATCH 12/19] can: mscan/mpc5xxx_can.c -- " Uwe Kleine-König
2023-05-12 21:37   ` Uwe Kleine-König
2023-05-12 21:27 ` [PATCH 13/19] can: rcar: " Uwe Kleine-König
2023-05-15  7:53   ` Geert Uytterhoeven
2023-05-12 21:27 ` [PATCH 14/19] can: sja1000_isa: " Uwe Kleine-König
2023-05-12 21:27 ` [PATCH 15/19] can: sja1000_platform: " Uwe Kleine-König
2023-05-12 21:27 ` [PATCH 16/19] can: softing: " Uwe Kleine-König
2023-05-12 21:27 ` [PATCH 17/19] can: sun4i_can: " Uwe Kleine-König
2023-05-13  6:36   ` Jernej Škrabec
2023-05-14 17:05   ` Gerhard Bertelsmann
2023-05-12 21:27 ` [PATCH 18/19] can: ti_hecc: " Uwe Kleine-König
2023-05-12 21:27 ` [PATCH 19/19] can: xilinx: " Uwe Kleine-König
2023-05-16  7:31 ` [PATCH net-next 00/19] can: " Simon Horman
2023-05-16  8:45   ` Simon Horman
2023-05-16  8:54     ` Marc Kleine-Budde
2023-05-16  8:56       ` Marc Kleine-Budde

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=6fd7b691-1a60-4ee3-7292-aa401de16aed@microchip.com \
    --to=claudiu.beznea@microchip.com \
    --cc=Nicolas.Ferre@microchip.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kernel@pengutronix.de \
    --cc=kuba@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-can@vger.kernel.org \
    --cc=mkl@pengutronix.de \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=u.kleine-koenig@pengutronix.de \
    --cc=wg@grandegger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox