linux-kernel - [tip: sched/core] sched: Fix a typo in a comment

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

Message-ID: <159593341116.4006.140505713819704674.tip-bot2@tip-bot2>
Date:   Tue, 28 Jul 2020 10:50:11 -0000
From:   tip-bot2 for 王文虎 <tip-bot2@...utronix.de>
To:     linux-tip-commits@...r.kernel.org
Cc:     Wang Wenhu <wenhu.wang@...o.com>, Ingo Molnar <mingo@...nel.org>,
        x86 <x86@...nel.org>, LKML <linux-kernel@...r.kernel.org>
Subject: [tip: sched/core] sched: Fix a typo in a comment

The following commit has been merged into the sched/core branch of tip:

Commit-ID:     c1b7b8d42b5422627b0a8268416a60748f8d000f
Gitweb:        https://git.kernel.org/tip/c1b7b8d42b5422627b0a8268416a60748f8d000f
Author:        王文虎 <wenhu.wang@...o.com>
AuthorDate:    Mon, 27 Jul 2020 21:39:51 +08:00
Committer:     Ingo Molnar <mingo@...nel.org>
CommitterDate: Mon, 27 Jul 2020 23:37:53 +02:00

sched: Fix a typo in a comment

Change the comment typo: "direcly" -> "directly".

Signed-off-by: Wang Wenhu <wenhu.wang@...o.com>
Signed-off-by: Ingo Molnar <mingo@...nel.org>
Link: https://lore.kernel.org/r/AAcAXwBTDSpsKN-5iyIOtaqk.1.1595857191899.Hmail.wenhu.wang@vivo.com
---
 include/linux/sched.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/include/linux/sched.h b/include/linux/sched.h
index 5033813..adf0125 100644
--- a/include/linux/sched.h
+++ b/include/linux/sched.h
@@ -374,7 +374,7 @@ struct util_est {
  * For cfs_rq, they are the aggregated values of all runnable and blocked
  * sched_entities.
  *
- * The load/runnable/util_avg doesn't direcly factor frequency scaling and CPU
+ * The load/runnable/util_avg doesn't directly factor frequency scaling and CPU
  * capacity scaling. The scaling is done through the rq_clock_pelt that is used
  * for computing those signals (see update_rq_clock_pelt())
  *