[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20211201071937.e6uso2qwzgtbfest@vireshk-i7>
Date: Wed, 1 Dec 2021 12:49:37 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Tang Yizhou <tangyizhou@...wei.com>
Cc: rafael.j.wysocki@...el.com, rafael@...nel.org,
linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org,
zhengbin13@...wei.com
Subject: Re: [PATCH v3 1/2] cpufreq: Fix a comment in cpufreq_policy_free
On 01-12-21, 15:40, Tang Yizhou wrote:
> Make the comment of blocking_notifier_call_chain() easier to
> understand.
>
> Signed-off-by: Tang Yizhou <tangyizhou@...wei.com>
> ---
> drivers/cpufreq/cpufreq.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/cpufreq/cpufreq.c b/drivers/cpufreq/cpufreq.c
> index e338d2f010fe..db0b4b4258d5 100644
> --- a/drivers/cpufreq/cpufreq.c
> +++ b/drivers/cpufreq/cpufreq.c
> @@ -1296,8 +1296,9 @@ static void cpufreq_policy_free(struct cpufreq_policy *policy)
>
> if (policy->max_freq_req) {
> /*
> - * CPUFREQ_CREATE_POLICY notification is sent only after
> - * successfully adding max_freq_req request.
> + * Remove max_freq_req after sending CPUFREQ_REMOVE_POLICY
> + * notification, since CPUFREQ_CREATE_POLICY notification was
> + * sent after adding max_freq_req earlier.
> */
> blocking_notifier_call_chain(&cpufreq_policy_notifier_list,
> CPUFREQ_REMOVE_POLICY, policy);
Acked-by: Viresh Kumar <viresh.kumar@...aro.org>
--
viresh
Powered by blists - more mailing lists