From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Andy Gross" <agross@kernel.org>,
"Bjorn Andersson" <andersson@kernel.org>,
"Wolfram Sang" <wsa@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, linux-i2c@vger.kernel.org,
kernel@pengutronix.de
Subject: Re: [PATCH 57/89] i2c: qup: Convert to platform remove callback returning void
Date: Tue, 9 May 2023 10:47:01 +0200 [thread overview]
Message-ID: <2ad329a7-d9ef-71fd-6d96-4c9743a3f8f9@linaro.org> (raw)
In-Reply-To: <20230508205306.1474415-58-u.kleine-koenig@pengutronix.de>
On 8.05.2023 22:52, 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 (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.
>
> Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> ---
Reviewed-by: Konrad Dybcio <konrad.dybcio@linaro.org>
Konrad
> drivers/i2c/busses/i2c-qup.c | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/i2c/busses/i2c-qup.c b/drivers/i2c/busses/i2c-qup.c
> index 2e153f2f71b6..6eef1dbd00de 100644
> --- a/drivers/i2c/busses/i2c-qup.c
> +++ b/drivers/i2c/busses/i2c-qup.c
> @@ -1904,7 +1904,7 @@ static int qup_i2c_probe(struct platform_device *pdev)
> return ret;
> }
>
> -static int qup_i2c_remove(struct platform_device *pdev)
> +static void qup_i2c_remove(struct platform_device *pdev)
> {
> struct qup_i2c_dev *qup = platform_get_drvdata(pdev);
>
> @@ -1918,7 +1918,6 @@ static int qup_i2c_remove(struct platform_device *pdev)
> i2c_del_adapter(&qup->adap);
> pm_runtime_disable(qup->dev);
> pm_runtime_set_suspended(qup->dev);
> - return 0;
> }
>
> #ifdef CONFIG_PM
> @@ -1978,7 +1977,7 @@ MODULE_DEVICE_TABLE(of, qup_i2c_dt_match);
>
> static struct platform_driver qup_i2c_driver = {
> .probe = qup_i2c_probe,
> - .remove = qup_i2c_remove,
> + .remove_new = qup_i2c_remove,
> .driver = {
> .name = "i2c_qup",
> .pm = &qup_i2c_qup_pm_ops,
next prev parent reply other threads:[~2023-05-09 8:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-08 20:51 [PATCH 00/89] i2c: Convert to platform remove callback returning void Uwe Kleine-König
2023-05-08 20:52 ` [PATCH 55/89] i2c: qcom-cci: " Uwe Kleine-König
2023-05-08 20:52 ` [PATCH 56/89] i2c: qcom-geni: " Uwe Kleine-König
2023-05-09 8:46 ` Konrad Dybcio
2023-05-08 20:52 ` [PATCH 57/89] i2c: qup: " Uwe Kleine-König
2023-05-09 8:47 ` Konrad Dybcio [this message]
2023-06-01 7:33 ` [PATCH 00/89] i2c: " Uwe Kleine-König
2023-06-01 7:43 ` Biju Das
2023-06-01 13:54 ` Wolfram Sang
2023-06-05 7:54 ` Wolfram Sang
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=2ad329a7-d9ef-71fd-6d96-4c9743a3f8f9@linaro.org \
--to=konrad.dybcio@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=kernel@pengutronix.de \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
--cc=wsa@kernel.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