[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <qnaqcauq3n6364hhet2dwrenb6s2jstwjxv7hlv5u6muvn3vf4@pu4pa5g4vrmw>
Date: Tue, 19 Sep 2023 08:04:18 +0000
From: Alvin Šipraga <ALSI@...g-olufsen.dk>
To: Uwe Kleine-König <u.kleine-koenig@...gutronix.de>
CC: Linus Walleij <linus.walleij@...aro.org>, Andrew Lunn <andrew@...n.ch>,
Florian Fainelli <f.fainelli@...il.com>, Vladimir Oltean <olteanv@...il.com>,
"David S. Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>, "kernel@...gutronix.de"
<kernel@...gutronix.de>
Subject: Re: [PATCH net-next 7/9] net: dsa: realtek: Convert to platform
remove callback returning void
On Mon, Sep 18, 2023 at 09:19:14PM +0200, 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() 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>
> ---
Reviewed-by: Alvin Šipraga <alsi@...g-olufsen.dk>
Powered by blists - more mailing lists