[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e8d411e1e01f3c7ae8bf97f2f1700e3d@gerhard-bertelsmann.de>
Date: Sun, 14 May 2023 19:05:08 +0200
From: Gerhard Bertelsmann <info@...hard-bertelsmann.de>
To: Uwe Kleine-König <u.kleine-koenig@...gutronix.de>
Cc: Wolfgang Grandegger <wg@...ndegger.com>, Marc Kleine-Budde
<mkl@...gutronix.de>, "David S. Miller" <davem@...emloft.net>, Eric Dumazet
<edumazet@...gle.com>, Jakub Kicinski <kuba@...nel.org>, Paolo Abeni
<pabeni@...hat.com>, Chen-Yu Tsai <wens@...e.org>, Jernej Skrabec
<jernej.skrabec@...il.com>, Samuel Holland <samuel@...lland.org>,
linux-can@...r.kernel.org, netdev@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-sunxi@...ts.linux.dev,
kernel@...gutronix.de
Subject: Re: [PATCH 17/19] can: sun4i_can: Convert to platform remove callback
returning void
Am 2023-05-12 23:27, schrieb Uwe Kleine-König:
> 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@...gutronix.de>
Acked-by: Gerhard Bertelsmann <info@...hard-bertelsmann.de>
Thanks Uwe :-)
Powered by blists - more mailing lists