Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp4404726ybl; Mon, 13 Jan 2020 13:07:47 -0800 (PST) X-Google-Smtp-Source: APXvYqzDQI+oQxPFyDbg0Swsqbpp8k+fz922V/O8uZsIbGxcec4fQTxUa/ZdCtxFN5OuojXkkbFD X-Received: by 2002:a05:6830:1d59:: with SMTP id p25mr14969810oth.308.1578949667395; Mon, 13 Jan 2020 13:07:47 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1578949667; cv=none; d=google.com; s=arc-20160816; b=Xu5QzIaPsjHmlvhjDXWGRhmorq7Bji0ORZorMg/NNJ4Wze0Nuo2TdrX+rbeJbJtgUt uC8cwqVpcyLF5AlZgGl3vyRu5DjB7cCSC+BB2QmulSvbqR8JLZ+o9dmOD3BugI8bdk/w kgmpymShqogGwoDbTX9hwsSCg0/NiUQIoMgTSiWaUE6P8yGC9949MW0YcABSYcBHnIvK cHplgo3XxZP5fSHeG+dk3REMsRkfW7PhfEbHlO3hXek/9Wv+tZQrnKxGKfWyPb13I7Q0 wOCzlwJYHLTDYPx3ID3sgEHs+zzx2wm2T4xeY8rB2mg5IO8ydJyMMlprALO9KEPu3enJ ICWA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date; bh=2rA7sSWEfDJToxJ/YgdWmlOio16Vu1Hmy3P+/r8uJTg=; b=Ppzasc2mytHsv3FZME0kskOlDwxnotWBEFc3otBUvJj9gUlV1QHKS2z896QkKXEWlp v4vIxhW8Y4FcYum4yurjD3fr48IG2/nBi6HqaK5OWLKdkV3N3BNnYJQvTGMcC84/Ed/h aP5eYrfZsAVAnmWQU9pLT209Al/Px/y6sWCKRGWVKdUwkGD62Atms3DpOlXkiRKFm43g L1Lxw4mayInNEfbbCmPNXs+c3QqE+jx61o7yqM+z6aSdQUGLUF6p3YUq5TgT7HXWa0Ln fMTF+1f+Hufk1OLz+gVjeDoO7TUCSAc5cUSdHpPqLdOQHbOqtz5cWn8Kc5dcozqkufAX gXtA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id a14si8221594otk.2.2020.01.13.13.07.34; Mon, 13 Jan 2020 13:07:47 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728799AbgAMVEQ (ORCPT + 99 others); Mon, 13 Jan 2020 16:04:16 -0500 Received: from mail.kernel.org ([198.145.29.99]:59932 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726086AbgAMVEQ (ORCPT ); Mon, 13 Jan 2020 16:04:16 -0500 Received: from gandalf.local.home (cpe-66-24-58-225.stny.res.rr.com [66.24.58.225]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 263A0206D7; Mon, 13 Jan 2020 21:04:15 +0000 (UTC) Date: Mon, 13 Jan 2020 16:04:13 -0500 From: Steven Rostedt To: Cc: Hewenliang , , , , , , Subject: Re: [PATCH] idle: fix spelling mistake "iterrupts" -> "interrupts" Message-ID: <20200113160413.5afcfbd7@gandalf.local.home> In-Reply-To: <20200110025604.34373-1-hewenliang4@huawei.com> References: <20200110025604.34373-1-hewenliang4@huawei.com> X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.32; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Peter, I guess you could just pull this into one of your queues. Reviewed-by: Steven Rostedt (VMware) -- Steve On Thu, 9 Jan 2020 21:56:04 -0500 Hewenliang wrote: > There is a spelling misake in comments of cpuidle_idle_call. Fix it. > > Signed-off-by: Hewenliang > --- > 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