[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <75d2dc5e-4cbf-2519-cdf7-8fde374126ec@linaro.org>
Date: Thu, 13 Jul 2023 10:11:15 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Yangtao Li <frank.li@...o.com>,
Jaehoon Chung <jh80.chung@...sung.com>,
Ulf Hansson <ulf.hansson@...aro.org>,
Alim Akhtar <alim.akhtar@...sung.com>
Cc: Uwe Kleine-König <u.kleine-koenig@...gutronix.de>,
linux-mmc@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-samsung-soc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 14/58] mmc: dw_mmc: exynos: Convert to platform remove
callback returning void
On 13/07/2023 10:07, Yangtao Li 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 (mostly) ignored
> 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.
>
> Trivially convert this driver from always returning zero in the remove
> callback to the void returning variant.
You even copied Uwe's commit msg... Aren't you duplicate his work or is
it being coordinated?
Best regards,
Krzysztof
Powered by blists - more mailing lists