[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230721054938.1666475-2-xiongwei.song@windriver.com>
Date: Fri, 21 Jul 2023 13:49:38 +0800
From: <xiongwei.song@...driver.com>
To: <tj@...nel.org>, <lizefan.x@...edance.com>, <hannes@...xchg.org>,
<corbet@....net>
CC: <cgroups@...r.kernel.org>, <linux-doc@...r.kernel.org>,
<linux-kernel@...r.kernel.org>
Subject: [PATCH 2/2] docs: cgroup-v1: fix typo
From: Xiongwei Song <xiongwei.song@...driver.com>
"listers" -> "listeners"
Signed-off-by: Xiongwei Song <xiongwei.song@...driver.com>
---
Documentation/admin-guide/cgroup-v1/memory.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/admin-guide/cgroup-v1/memory.rst b/Documentation/admin-guide/cgroup-v1/memory.rst
index dcb65b49bb22..1f239fa938c2 100644
--- a/Documentation/admin-guide/cgroup-v1/memory.rst
+++ b/Documentation/admin-guide/cgroup-v1/memory.rst
@@ -909,7 +909,7 @@ experiences some pressure. In this situation, only group C will receive the
notification, i.e. groups A and B will not receive it. This is done to avoid
excessive "broadcasting" of messages, which disturbs the system and which is
especially bad if we are low on memory or thrashing. Group B, will receive
-notification only if there are no event listers for group C.
+notification only if there are no event listeners for group C.
There are three optional modes that specify different propagation behavior:
--
2.25.1
Powered by blists - more mailing lists