summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAtul Kumar Pant <atulpant.linux@gmail.com>2025-04-05 11:39:09 +0530
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>2025-04-09 19:34:23 +0200
commit194c396e8a0d25f06dfb02683f8e33727a58882f (patch)
treee4d5c542861ebf8dab865b59c66319f47ba77e2e
parent0af2f6be1b4281385b618cb86ad946eded089ac8 (diff)
cpuidle: teo: Fix typos in two comments
Fix a typo and correct a spelling mistake in comments. Signed-off-by: Atul Kumar Pant <atulpant.linux@gmail.com> Link: https://patch.msgid.link/20250405060909.2026332-1-atulpant.linux@gmail.com [ rjw: Subject and changelog edits ] Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
-rw-r--r--drivers/cpuidle/governors/teo.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/drivers/cpuidle/governors/teo.c b/drivers/cpuidle/governors/teo.c
index 8fe5e1b47ef9..bfa55c1eab5b 100644
--- a/drivers/cpuidle/governors/teo.c
+++ b/drivers/cpuidle/governors/teo.c
@@ -19,7 +19,7 @@
*
* Of course, non-timer wakeup sources are more important in some use cases,
* but even then it is generally unnecessary to consider idle duration values
- * greater than the time time till the next timer event, referred as the sleep
+ * greater than the time till the next timer event, referred as the sleep
* length in what follows, because the closest timer will ultimately wake up the
* CPU anyway unless it is woken up earlier.
*
@@ -311,7 +311,7 @@ static int teo_select(struct cpuidle_driver *drv, struct cpuidle_device *dev,
struct cpuidle_state *s = &drv->states[i];
/*
- * Update the sums of idle state mertics for all of the states
+ * Update the sums of idle state metrics for all of the states
* shallower than the current one.
*/
intercept_sum += prev_bin->intercepts;