From: "Jernej Škrabec" <jernej.skrabec@gmail.com>
To: "Arnd Bergmann" <arnd@arndb.de>, "Chen-Yu Tsai" <wens@csie.org>,
"Samuel Holland" <samuel@sholland.org>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: linux-arm-kernel@lists.infradead.org,
linux-sunxi@lists.linux.dev, linux-kernel@vger.kernel.org,
kernel@pengutronix.de
Subject: Re: [PATCH 06/12] bus: sun50i-de2: Convert to platform remove callback returning void
Date: Sat, 18 Nov 2023 22:50:33 +0100 [thread overview]
Message-ID: <5727528.DvuYhMxLoT@jernej-laptop> (raw)
In-Reply-To: <20231109202830.4124591-7-u.kleine-koenig@pengutronix.de>
Dne četrtek, 09. november 2023 ob 21:28:36 CET je Uwe Kleine-König napisal(a):
> 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>
Reviewed-by: Jernej Skrabec <jernej.skrabec@gmail.com>
Best regards,
Jernej
> ---
> drivers/bus/sun50i-de2.c | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/bus/sun50i-de2.c b/drivers/bus/sun50i-de2.c
> index 414f29cdedf0..3339311ce068 100644
> --- a/drivers/bus/sun50i-de2.c
> +++ b/drivers/bus/sun50i-de2.c
> @@ -24,10 +24,9 @@ static int sun50i_de2_bus_probe(struct platform_device *pdev)
> return 0;
> }
>
> -static int sun50i_de2_bus_remove(struct platform_device *pdev)
> +static void sun50i_de2_bus_remove(struct platform_device *pdev)
> {
> sunxi_sram_release(&pdev->dev);
> - return 0;
> }
>
> static const struct of_device_id sun50i_de2_bus_of_match[] = {
> @@ -37,7 +36,7 @@ static const struct of_device_id sun50i_de2_bus_of_match[] = {
>
> static struct platform_driver sun50i_de2_bus_driver = {
> .probe = sun50i_de2_bus_probe,
> - .remove = sun50i_de2_bus_remove,
> + .remove_new = sun50i_de2_bus_remove,
> .driver = {
> .name = "sun50i-de2-bus",
> .of_match_table = sun50i_de2_bus_of_match,
>
_______________________________________________
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:[~2023-11-18 21:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-09 20:28 [PATCH 00/12] bus: Convert to platform remove callback returning void Uwe Kleine-König
2023-11-09 20:28 ` [PATCH 06/12] bus: sun50i-de2: " Uwe Kleine-König
2023-11-10 10:18 ` Andre Przywara
2023-11-18 21:50 ` Jernej Škrabec [this message]
2023-11-09 20:28 ` [PATCH 07/12] bus: sunxi-rsb: " Uwe Kleine-König
2023-11-10 10:20 ` Andre Przywara
2023-11-18 21:51 ` Jernej Škrabec
2023-11-10 6:32 ` [PATCH 00/12] bus: " Arnd Bergmann
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=5727528.DvuYhMxLoT@jernej-laptop \
--to=jernej.skrabec@gmail.com \
--cc=arnd@arndb.de \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=samuel@sholland.org \
--cc=u.kleine-koenig@pengutronix.de \
--cc=wens@csie.org \
/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