linux-kernel - Re: [PATCH 3/3] cpuidle: Trivial fixes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Tue, 10 Dec 2019 09:14:26 +0000
From:   Mukesh Ojha <mojha@...eaurora.org>
To:     trivial@...nel.org, mingo@...hat.com, juri.lelli@...hat.com,
        peterz@...radead.org, linux-kernel@...r.kernel.org
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 <mojha@...eaurora.org>
> ---
>   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.