[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200513141854.18451-1-wenhu.wang@vivo.com>
Date: Wed, 13 May 2020 07:18:54 -0700
From: Wang Wenhu <wenhu.wang@...o.com>
To: rjw@...ysocki.net, viresh.kumar@...aro.org,
linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org
Cc: kernel@...o.com, Wang Wenhu <wenhu.wang@...o.com>
Subject: [PATCH] cpufreq: fix a minor typo for cpufreq_driver doc
Delete the duplicate "to" possibly double-typed.
Signed-off-by: Wang Wenhu <wenhu.wang@...o.com>
Cc: Viresh Kumar <viresh.kumar@...aro.org>
---
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 f7240251a949..67d5950bd878 100644
--- a/include/linux/cpufreq.h
+++ b/include/linux/cpufreq.h
@@ -330,7 +330,7 @@ struct cpufreq_driver {
*
* get_intermediate should return a stable intermediate frequency
* platform wants to switch to and target_intermediate() should set CPU
- * to to that frequency, before jumping to the frequency corresponding
+ * to that frequency, before jumping to the frequency corresponding
* to 'index'. Core will take care of sending notifications and driver
* doesn't have to handle them in target_intermediate() or
* target_index().
--
2.17.1
Powered by blists - more mailing lists