From: Zhongqiu Han <zhongqiu.han@oss.qualcomm.com>
To: Viresh Kumar <viresh.kumar@linaro.org>,
"Rafael J. Wysocki" <rafael@kernel.org>
Cc: linux-pm@vger.kernel.org,
Vincent Guittot <vincent.guittot@linaro.org>,
Sumit Semwal <sumit.semwal@linaro.org>,
Lifeng Zheng <zhenglifeng1@huawei.com>,
linux-kernel@vger.kernel.org, zhongqiu.han@oss.qualcomm.com
Subject: Re: [PATCH 1/3] cpufreq: Fix typo in comment
Date: Thu, 21 May 2026 20:59:46 +0800 [thread overview]
Message-ID: <ece93532-6822-48ce-af84-c118cf4cc749@oss.qualcomm.com> (raw)
In-Reply-To: <6fef156008fc6b70069f3cfedb7de02fe54f2696.1779360823.git.viresh.kumar@linaro.org>
On 5/21/2026 7:39 PM, Viresh Kumar wrote:
> Replace "diver" with "driver" in the comment describing
> CPUFREQ_NEED_UPDATE_LIMITS.
>
> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
Looks good to me.
Reviewed-by: Zhongqiu Han <zhongqiu.han@oss.qualcomm.com>
> ---
> include/linux/cpufreq.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/linux/cpufreq.h b/include/linux/cpufreq.h
> index 2ab691828e48..4d4b4ed24b30 100644
> --- a/include/linux/cpufreq.h
> +++ b/include/linux/cpufreq.h
> @@ -434,7 +434,7 @@ struct cpufreq_driver {
> /*
> * Set by drivers that need to update internal upper and lower boundaries along
> * with the target frequency and so the core and governors should also invoke
> - * the diver if the target frequency does not change, but the policy min or max
> + * the driver if the target frequency does not change, but the policy min or max
> * may have changed.
> */
> #define CPUFREQ_NEED_UPDATE_LIMITS BIT(0)
--
Thx and BRs,
Zhongqiu Han
prev parent reply other threads:[~2026-05-21 12:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-21 11:39 Viresh Kumar
2026-05-21 11:39 ` [PATCH 2/3] cpufreq: Avoid redundant target() calls for unchanged limits Viresh Kumar
2026-05-21 13:58 ` Zhongqiu Han
2026-05-21 14:33 ` Viresh Kumar
2026-05-21 20:40 ` Rafael J. Wysocki
2026-05-21 11:39 ` [PATCH V2 3/3] cpufreq: conservative: Simplify frequency limit handling Viresh Kumar
2026-05-21 12:22 ` [PATCH 1/3] cpufreq: Fix typo in comment zhenglifeng (A)
2026-05-21 14:29 ` Viresh Kumar
2026-05-21 12:59 ` Zhongqiu Han [this message]
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=ece93532-6822-48ce-af84-c118cf4cc749@oss.qualcomm.com \
--to=zhongqiu.han@oss.qualcomm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=sumit.semwal@linaro.org \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@linaro.org \
--cc=zhenglifeng1@huawei.com \
/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®