mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: <peterz@infradead.org>
Cc: Hewenliang <hewenliang4@huawei.com>, <mingo@redhat.com>,
	<juri.lelli@redhat.com>, <vincent.guittot@linaro.org>,
	<bsegall@google.com>, <mgorman@suse.de>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] idle: fix spelling mistake "iterrupts" -> "interrupts"
Date: Mon, 13 Jan 2020 16:04:13 -0500	[thread overview]
Message-ID: <20200113160413.5afcfbd7@gandalf.local.home> (raw)
In-Reply-To: <20200110025604.34373-1-hewenliang4@huawei.com>


Peter,

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

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

-- Steve


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

> There is a spelling misake in comments of cpuidle_idle_call. Fix it.
> 
> Signed-off-by: Hewenliang <hewenliang4@huawei.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


  reply	other threads:[~2020-01-13 21:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-10  2:56 Hewenliang
2020-01-13 21:04 ` Steven Rostedt [this message]
2020-01-14 10:02   ` Peter Zijlstra
2020-01-14 14:16     ` Steven Rostedt
2020-01-17 10:08 ` [tip: sched/core] " tip-bot2 for Hewenliang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200113160413.5afcfbd7@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=bsegall@google.com \
    --cc=hewenliang4@huawei.com \
    --cc=juri.lelli@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgorman@suse.de \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=vincent.guittot@linaro.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®