linux-kernel - Re: [PATCH] idle: fix spelling mistake "iterrupts" -> "interrupts"

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20200113160413.5afcfbd7@gandalf.local.home>
Date:   Mon, 13 Jan 2020 16:04:13 -0500
From:   Steven Rostedt <rostedt@...dmis.org>
To:     <peterz@...radead.org>
Cc:     Hewenliang <hewenliang4@...wei.com>, <mingo@...hat.com>,
        <juri.lelli@...hat.com>, <vincent.guittot@...aro.org>,
        <bsegall@...gle.com>, <mgorman@...e.de>,
        <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] idle: fix spelling mistake "iterrupts" -> "interrupts"


Peter,

I guess you could just pull this into one of your queues.

Reviewed-by: Steven Rostedt (VMware) <rostedt@...dmis.org>

-- Steve


On Thu, 9 Jan 2020 21:56:04 -0500
Hewenliang <hewenliang4@...wei.com> wrote:

> There is a spelling misake in comments of cpuidle_idle_call. Fix it.
> 
> Signed-off-by: Hewenliang <hewenliang4@...wei.com>
> ---
>  kernel/sched/idle.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/kernel/sched/idle.c b/kernel/sched/idle.c
> index f65ef1e2f204..d29ebe8c63dd 100644
> --- a/kernel/sched/idle.c
> +++ b/kernel/sched/idle.c
> @@ -158,7 +158,7 @@ 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
> +	 * activity happens here and in interrupts (if any). In that case bypass
>  	 * the cpuidle governor and go stratight 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