From: "tip-bot2 for Hewenliang" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Hewenliang <hewenliang4@huawei.com>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
"Steven Rostedt (VMware)" <rostedt@goodmis.org>,
x86 <x86@kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: [tip: sched/core] idle: fix spelling mistake "iterrupts" -> "interrupts"
Date: Fri, 17 Jan 2020 10:08:40 -0000 [thread overview]
Message-ID: <157925572055.396.10697981012861050378.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20200110025604.34373-1-hewenliang4@huawei.com>
The following commit has been merged into the sched/core branch of tip:
Commit-ID: 3e0de271fff77abb933f1b69c213854c3eda9125
Gitweb: https://git.kernel.org/tip/3e0de271fff77abb933f1b69c213854c3eda9125
Author: Hewenliang <hewenliang4@huawei.com>
AuthorDate: Thu, 09 Jan 2020 21:56:04 -05:00
Committer: Peter Zijlstra <peterz@infradead.org>
CommitterDate: Fri, 17 Jan 2020 10:19:22 +01:00
idle: fix spelling mistake "iterrupts" -> "interrupts"
There is a spelling misake in comments of cpuidle_idle_call. Fix it.
Signed-off-by: Hewenliang <hewenliang4@huawei.com>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Reviewed-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
Link: https://lkml.kernel.org/r/20200110025604.34373-1-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 ffa959e..b743bf3 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
prev parent reply other threads:[~2020-01-17 10:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-10 2:56 [PATCH] " Hewenliang
2020-01-13 21:04 ` Steven Rostedt
2020-01-14 10:02 ` Peter Zijlstra
2020-01-14 14:16 ` Steven Rostedt
2020-01-17 10:08 ` tip-bot2 for Hewenliang [this message]
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=157925572055.396.10697981012861050378.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=hewenliang4@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=x86@kernel.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®