From: Viresh Kumar <viresh.kumar@linaro.org>
To: David Arcari <darcari@redhat.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>
Cc: linux-acpi@vger.kernel.org
Subject: Re: [PATCH] cpufreq: cpufreq_register_driver should return -ENODEV if init fails
Date: Mon, 29 May 2017 10:02:15 +0530 [thread overview]
Message-ID: <20170529043215.GA5752@vireshk-i7> (raw)
In-Reply-To: <1495813051-146077-1-git-send-email-darcari@redhat.com>
You sent it to the wrong list and missed Rafael too. MAINTAINERS file should
help getting these details in the future.
On 26-05-17, 11:37, David Arcari wrote:
> For a driver that does not set the CPUFREQ_STICKY flag, if all of the
> ->init() calls fail, cpufreq_register_driver() should return an error.
> This will prevent the driver from loading.
>
> Fixes: ce1bcfe94db8 ("cpufreq: check cpufreq_policy_list instead of scanning policies for all CPUs")
>
> Cc: Viresh Kumar <viresh.kumar@linaro.org>
> Signed-off-by: David Arcari <darcari@redhat.com>
+
Cc: 4.0+ <stable@vger.kernel.org> # 4.0+
> ---
> drivers/cpufreq/cpufreq.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/cpufreq/cpufreq.c b/drivers/cpufreq/cpufreq.c
> index 0e3f649..26b643d 100644
> --- a/drivers/cpufreq/cpufreq.c
> +++ b/drivers/cpufreq/cpufreq.c
> @@ -2468,6 +2468,7 @@ int cpufreq_register_driver(struct cpufreq_driver *driver_data)
> if (!(cpufreq_driver->flags & CPUFREQ_STICKY) &&
> list_empty(&cpufreq_policy_list)) {
> /* if all ->init() calls failed, unregister */
> + ret = -ENODEV;
> pr_debug("%s: No CPU initialized for driver %s\n", __func__,
> driver_data->name);
> goto err_if_unreg;
Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
--
viresh
next parent reply other threads:[~2017-05-29 4:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1495813051-146077-1-git-send-email-darcari@redhat.com>
2017-05-29 4:32 ` Viresh Kumar [this message]
2017-05-30 12:05 ` [PATCH] cpufreq: cpufreq_register_driver should return -ENODEV if init fails David Arcari
2017-05-30 21:42 ` Rafael J. Wysocki
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=20170529043215.GA5752@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=darcari@redhat.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
/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;
as well as URLs for NNTP newsgroup(s).