[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20241112025724.474881-1-xiujianfeng@huaweicloud.com>
Date: Tue, 12 Nov 2024 02:57:24 +0000
From: Xiu Jianfeng <xiujianfeng@...weicloud.com>
To: peterz@...radead.org,
mingo@...hat.com,
will@...nel.org,
longman@...hat.com,
boqun.feng@...il.com,
corbet@....net
Cc: linux-kernel@...r.kernel.org,
linux-doc@...r.kernel.org
Subject: [PATCH -next] docs/locking: Fix grammar in percpu-rw-semaphore.rst
From: Xiu Jianfeng <xiujianfeng@...wei.com>
s/'is initialized'/'is initialized with'
Signed-off-by: Xiu Jianfeng <xiujianfeng@...wei.com>
---
Documentation/locking/percpu-rw-semaphore.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/locking/percpu-rw-semaphore.rst b/Documentation/locking/percpu-rw-semaphore.rst
index 247de6410855..a105bf2dd812 100644
--- a/Documentation/locking/percpu-rw-semaphore.rst
+++ b/Documentation/locking/percpu-rw-semaphore.rst
@@ -16,8 +16,8 @@ writing is very expensive, it calls synchronize_rcu() that can take
hundreds of milliseconds.
The lock is declared with "struct percpu_rw_semaphore" type.
-The lock is initialized percpu_init_rwsem, it returns 0 on success and
--ENOMEM on allocation failure.
+The lock is initialized with percpu_init_rwsem, it returns 0 on success
+and -ENOMEM on allocation failure.
The lock must be freed with percpu_free_rwsem to avoid memory leak.
The lock is locked for read with percpu_down_read, percpu_up_read and
--
2.34.1
Powered by blists - more mailing lists