[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200110025604.34373-1-hewenliang4@huawei.com>
Date: Thu, 9 Jan 2020 21:56:04 -0500
From: Hewenliang <hewenliang4@...wei.com>
To: <rostedt@...dmis.org>, <mingo@...hat.com>, <peterz@...radead.org>,
<juri.lelli@...hat.com>, <vincent.guittot@...aro.org>,
<bsegall@...gle.com>, <mgorman@...e.de>,
<linux-kernel@...r.kernel.org>
CC: <hewenliang4@...wei.com>
Subject: [PATCH] idle: fix spelling mistake "iterrupts" -> "interrupts"
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
--
2.19.1
Powered by blists - more mailing lists