[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAJZ5v0gu+5P=rnM=JC67kC-6dfO2P00oMBh7=73j+Et8beas3A@mail.gmail.com>
Date: Wed, 9 Apr 2025 19:35:53 +0200
From: "Rafael J. Wysocki" <rafael@...nel.org>
To: Atul Kumar Pant <atulpant.linux@...il.com>
Cc: rafael@...nel.org, daniel.lezcano@...aro.org, linux-pm@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] cpuidle: governors: Fixes typos in comments
On Sat, Apr 5, 2025 at 8:09 AM Atul Kumar Pant <atulpant.linux@...il.com> wrote:
>
> Fixes typos and corrects spelling in the comments.
>
> Signed-off-by: Atul Kumar Pant <atulpant.linux@...il.com>
> ---
> drivers/cpuidle/governors/teo.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/cpuidle/governors/teo.c b/drivers/cpuidle/governors/teo.c
> index 8fe5e1b47..bfa55c1ea 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;
> --
Applied as 6.16 material with some edits in the subject and changelog, thanks!
Powered by blists - more mailing lists