Skip to contentSkip to conversation

cpufreq: intel_pstate: Remove repeated word

PATCH Applied Nigel Christian 2 participants 2 messages Jan 17, 2021 – Jan 22, 2021

Subsystems (3)
Kernel janitors CPU frequency scaling framework Intel pstate driver
lore
Share & tools
lore

Nigel Christian

author
#0 lore raw

PATCH 1/1 cpufreq: intel_pstate: Remove repeated word

In the comment for trace in passive mode there is an unnecessary "the". Eradicate it.

Signed-off-by Nigel Christian <[email protected]>
---
 drivers/cpufreq/intel_pstate.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/cpufreq/intel_pstate.c +1 -1
index 6f2ff2775664..5175ae3cac44 100644
@@ -2498,7 +2498,7 @@ static int intel_cpufreq_verify_policy(struct cpufreq_policy_data *policy)
  * driver call was via the normal or fast switch path. Various graphs
  * output from the intel_pstate_tracer.py utility that include core_busy
  * (or performance or core_avg_perf) have a fixed y-axis from 0 to 100%,
- * so we use 10 to indicate the the normal path through the driver, and
+ * so we use 10 to indicate the normal path through the driver, and
  * 90 to indicate the fast switch path through the driver.
  * The scaled_busy field is not used, and is set to 0.
  */
Signature · 1 line
2.29.2
maintainer Applied
#1 lore raw
Quoted 14 lines · Nigel Christian

In the comment for trace in passive mode there is an unnecessary "the". Eradicate it.

Signed-off-by Nigel Christian <[email protected]>
---
 drivers/cpufreq/intel_pstate.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/cpufreq/intel_pstate.c +0 -0
index 6f2ff2775664..5175ae3cac44 100644

drivers/cpufreq/intel_pstate.c static int intel_cpufreq_verify_policy(struct cpufreq_policy_data *policy)

Quoted 9 lines
drivers/cpufreq/intel_pstate.c +1 -2
@@ -2498,7 +2498,7 @@ static int intel_cpufreq_verify_policy(struct cpufreq_policy_data *policy)
  * driver call was via the normal or fast switch path. Various graphs
  * output from the intel_pstate_tracer.py utility that include core_busy
  * (or performance or core_avg_perf) have a fixed y-axis from 0 to 100%,
- * so we use 10 to indicate the the normal path through the driver, and
+ * so we use 10 to indicate the normal path through the driver, and
  * 90 to indicate the fast switch path through the driver.
  * The scaled_busy field is not used, and is set to 0.
  */
--

Applied as 5.12 material, thanks!