2019-10-15 07:38:06

by Mukesh Ojha

[permalink] [raw]
Subject: [PATCH 3/3] cpuidle: Trivial fixes

iterrupts => interrupts
stratight => straight

Minor comment correction.

Signed-off-by: Mukesh Ojha <[email protected]>
---
kernel/sched/idle.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/kernel/sched/idle.c b/kernel/sched/idle.c
index 8dad5aa..2df8ae1 100644
--- a/kernel/sched/idle.c
+++ b/kernel/sched/idle.c
@@ -158,8 +158,8 @@ static void cpuidle_idle_call(void)
/*
* Suspend-to-idle ("s2idle") is a system state in which all user space
* has been frozen, all I/O devices have been suspended and the only
- * activity happens here and in iterrupts (if any). In that case bypass
- * the cpuidle governor and go stratight for the deepest idle state
+ * activity happens here is in interrupts (if any). In that case bypass
+ * the cpuidle governor and go straight for the deepest idle state
* available. Possibly also suspend the local tick and the entire
* timekeeping to prevent timer interrupts from kicking us out of idle
* until a proper wakeup interrupt happens.
--
Qualcomm India Private Limited, on behalf of Qualcomm Innovation Center,
Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project


2019-12-10 09:15:32

by Mukesh Ojha

[permalink] [raw]
Subject: Re: [PATCH 3/3] cpuidle: Trivial fixes

Gentle reminder.

On 10/15/2019 1:05 PM, Mukesh Ojha wrote:
> iterrupts => interrupts
> stratight => straight
>
> Minor comment correction.
>
> Signed-off-by: Mukesh Ojha <[email protected]>
> ---
> kernel/sched/idle.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/sched/idle.c b/kernel/sched/idle.c
> index 8dad5aa..2df8ae1 100644
> --- a/kernel/sched/idle.c
> +++ b/kernel/sched/idle.c
> @@ -158,8 +158,8 @@ static void cpuidle_idle_call(void)
> /*
> * Suspend-to-idle ("s2idle") is a system state in which all user space
> * has been frozen, all I/O devices have been suspended and the only
> - * activity happens here and in iterrupts (if any). In that case bypass
> - * the cpuidle governor and go stratight for the deepest idle state
> + * activity happens here is in interrupts (if any). In that case bypass
> + * the cpuidle governor and go straight for the deepest idle state
> * available. Possibly also suspend the local tick and the entire
> * timekeeping to prevent timer interrupts from kicking us out of idle
> * until a proper wakeup interrupt happens.