[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240903024753.104609-1-bagasdotme@gmail.com>
Date: Tue, 3 Sep 2024 09:47:53 +0700
From: Bagas Sanjaya <bagasdotme@...il.com>
To: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Documentation <linux-doc@...r.kernel.org>,
Linux Kernel Livepatching <live-patching@...r.kernel.org>
Cc: Josh Poimboeuf <jpoimboe@...nel.org>,
Jiri Kosina <jikos@...nel.org>,
Miroslav Benes <mbenes@...e.cz>,
Petr Mladek <pmladek@...e.com>,
Joe Lawrence <joe.lawrence@...hat.com>,
Jonathan Corbet <corbet@....net>,
Marcos Paulo de Souza <mpdesouza@...e.com>,
Bagas Sanjaya <bagasdotme@...il.com>
Subject: [PATCH] Documentation: livepatch: Correct release locks antonym
"get" doesn't properly fit as an antonym for "release" in the context
of locking. Correct it with "acquire".
Signed-off-by: Bagas Sanjaya <bagasdotme@...il.com>
---
Documentation/livepatch/livepatch.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/livepatch/livepatch.rst b/Documentation/livepatch/livepatch.rst
index 68e3651e8af925..acb90164929e32 100644
--- a/Documentation/livepatch/livepatch.rst
+++ b/Documentation/livepatch/livepatch.rst
@@ -50,7 +50,7 @@ some limitations, see below.
3. Consistency model
====================
-Functions are there for a reason. They take some input parameters, get or
+Functions are there for a reason. They take some input parameters, acquire or
release locks, read, process, and even write some data in a defined way,
have return values. In other words, each function has a defined semantic.
--
An old man doll... just what I always wanted! - Clara
Powered by blists - more mailing lists