From: Stephen Boyd <sboyd@kernel.org>
To: "Andy Gross" <agross@kernel.org>,
"Bjorn Andersson" <andersson@kernel.org>,
"Konrad Dybcio" <konrad.dybcio@linaro.org>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Michael Turquette <mturquette@baylibre.com>,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
kernel@pengutronix.de
Subject: Re: [PATCH] clk: qcom: cbf-msm8996: Convert to platform remove callback returning void
Date: Mon, 11 Sep 2023 13:02:53 -0700 [thread overview]
Message-ID: <8ec473b5b80d5fad8d76df6d88d2c1d0.sboyd@kernel.org> (raw)
In-Reply-To: <20230911151548.672485-1-u.kleine-koenig@pengutronix.de>
Quoting Uwe Kleine-König (2023-09-11 08:15:48)
> 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().
>
> qcom_msm8996_cbf_icc_remove() returned zero unconditionally. After
> changing this function to return void instead, the driver can be
> converted trivially to use .remove_new().
>
> Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> ---
Do you want to take this? Otherwise, I can apply it to fixes.
> drivers/clk/qcom/clk-cbf-8996.c | 12 +++++-------
> 1 file changed, 5 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/clk/qcom/clk-cbf-8996.c b/drivers/clk/qcom/clk-cbf-8996.c
> index 53f205a3f183..fe24b4abeab4 100644
> --- a/drivers/clk/qcom/clk-cbf-8996.c
> +++ b/drivers/clk/qcom/clk-cbf-8996.c
> @@ -250,13 +250,11 @@ static int qcom_msm8996_cbf_icc_register(struct platform_device *pdev, struct cl
> return 0;
> }
>
> -static int qcom_msm8996_cbf_icc_remove(struct platform_device *pdev)
> +static void qcom_msm8996_cbf_icc_remove(struct platform_device *pdev)
> {
> struct icc_provider *provider = platform_get_drvdata(pdev);
>
> icc_clk_unregister(provider);
> -
> - return 0;
> }
> #define qcom_msm8996_cbf_icc_sync_state icc_sync_state
> #else
> @@ -266,7 +264,7 @@ static int qcom_msm8996_cbf_icc_register(struct platform_device *pdev, struct c
>
> return 0;
> }
> -#define qcom_msm8996_cbf_icc_remove(pdev) (0)
> +#define qcom_msm8996_cbf_icc_remove(pdev) { }
It would be better if this was a static inline function.
> #define qcom_msm8996_cbf_icc_sync_state NULL
> #endif
>
next prev parent reply other threads:[~2023-09-11 21:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 15:15 [PATCH] clk: qcom: cbf-msm8996: Convert to platform remove callback returning void Uwe Kleine-König
2023-09-11 20:02 ` Stephen Boyd [this message]
2023-09-12 6:53 ` Uwe Kleine-König
2023-09-20 17:29 ` Bjorn Andersson
2023-10-10 3:49 ` Stephen Boyd
2023-10-20 15:50 ` Uwe Kleine-König
2023-10-21 15:58 ` Bjorn Andersson
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=8ec473b5b80d5fad8d76df6d88d2c1d0.sboyd@kernel.org \
--to=sboyd@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=kernel@pengutronix.de \
--cc=konrad.dybcio@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=u.kleine-koenig@pengutronix.de \
/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