From: "Александра Дюпина" <adiupina@astralinux.ru>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: Cristian Marussi <cristian.marussi@arm.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
linux-arm-kernel@lists.infradead.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, lvc-project@linuxtesting.org
Subject: Re: [PATCH] cpufreq: scmi: process the result of devm_of_clk_add_hw_provider()
Date: Fri, 17 Nov 2023 14:14:13 +0300 [thread overview]
Message-ID: <fe85f03b-1c2a-3a99-c62b-abdf7e1eccb4@astralinux.ru> (raw)
In-Reply-To: <20231117074911.14427-1-adiupina@astralinux.ru>
I'm sorry, I forgot to add "return ret;" after
calling the dev_err() function. Before I post
the second version of the patch, please let me
know what you think about this fix, keeping in
mind what I wanted to add "return ret;"
17.11.2023 10:49, Alexandra Diupina пишет:
> devm_of_clk_add_hw_provider() may return an errno, so
> add a return value check
>
> Found by Linux Verification Center (linuxtesting.org) with SVACE.
>
> Fixes: 8410e7f3b31e ("cpufreq: scmi: Fix OPP addition failure with a dummy clock provider")
> Signed-off-by: Alexandra Diupina <adiupina@astralinux.ru>
> ---
> drivers/cpufreq/scmi-cpufreq.c | 9 +++++++--
> 1 file changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/cpufreq/scmi-cpufreq.c b/drivers/cpufreq/scmi-cpufreq.c
> index c8a7ccc42c16..4037945663bf 100644
> --- a/drivers/cpufreq/scmi-cpufreq.c
> +++ b/drivers/cpufreq/scmi-cpufreq.c
> @@ -334,8 +334,13 @@ static int scmi_cpufreq_probe(struct scmi_device *sdev)
>
> #ifdef CONFIG_COMMON_CLK
> /* dummy clock provider as needed by OPP if clocks property is used */
> - if (of_property_present(dev->of_node, "#clock-cells"))
> - devm_of_clk_add_hw_provider(dev, of_clk_hw_simple_get, NULL);
> + if (of_property_present(dev->of_node, "#clock-cells")) {
> + ret = devm_of_clk_add_hw_provider(dev, of_clk_hw_simple_get, NULL);
> + if (ret) {
> + dev_err(dev, "%s: registering clock provider failed, err: %d\n",
> + __func__, ret);
> + }
> + }
> #endif
>
> ret = cpufreq_register_driver(&scmi_cpufreq_driver);
Regards,
Alexandra Diupina
next prev parent reply other threads:[~2023-11-17 11:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-17 7:49 Alexandra Diupina
2023-11-17 11:14 ` Александра Дюпина [this message]
2023-11-18 7:00 ` Christophe JAILLET
2023-12-05 15:12 ` [PATCH v2] " Alexandra Diupina
2023-12-06 6:11 ` Viresh Kumar
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=fe85f03b-1c2a-3a99-c62b-abdf7e1eccb4@astralinux.ru \
--to=adiupina@astralinux.ru \
--cc=cristian.marussi@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=rafael@kernel.org \
--cc=sudeep.holla@arm.com \
--cc=viresh.kumar@linaro.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
all inboxes | Powered by JetHome®