From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>,
Linux Kernel Livepatching <live-patching@vger.kernel.org>
Cc: Josh Poimboeuf <jpoimboe@kernel.org>,
Jiri Kosina <jikos@kernel.org>, Miroslav Benes <mbenes@suse.cz>,
Petr Mladek <pmladek@suse.com>,
Joe Lawrence <joe.lawrence@redhat.com>,
Jonathan Corbet <corbet@lwn.net>,
Attreyee Mukherjee <tintinm2017@gmail.com>,
Bagas Sanjaya <bagasdotme@gmail.com>
Subject: [PATCH 2/2] Documentation: livepatch: Correct opposite of releasing locks
Date: Wed, 29 Nov 2023 20:25:27 +0700 [thread overview]
Message-ID: <20231129132527.8078-3-bagasdotme@gmail.com> (raw)
In-Reply-To: <20231129132527.8078-1-bagasdotme@gmail.com>
The opposite action of releasing locks is acquiring them, not getting
them (as in configuration options; the inverse of such action is
setting options). Correct it.
Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.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 000059b3cbde49..53b49dafd7ded8 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
next prev parent reply other threads:[~2023-11-29 13:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-29 13:25 [PATCH 0/2] Minor grammatical fixup for livepatch docs Bagas Sanjaya
2023-11-29 13:25 ` [PATCH 1/2] Documentation: livepatch: Correct "step on each other's toes" idiom Bagas Sanjaya
2023-11-29 13:25 ` Bagas Sanjaya [this message]
2023-11-29 13:53 ` [PATCH 0/2] Minor grammatical fixup for livepatch docs Joe Lawrence
2023-11-29 23:58 ` Bagas Sanjaya
2023-11-30 0:08 ` Matthew Wilcox
2023-11-30 3:25 ` Bagas Sanjaya
2023-11-30 0:10 ` Jonathan Corbet
2023-11-30 8:04 ` Bagas Sanjaya
2023-11-29 14:29 ` Jonathan Corbet
2023-11-29 15:26 ` Matthew Wilcox
2023-11-30 0:13 ` Bagas Sanjaya
[not found] ` <CAJjsb4r5S80ZqdX3EnucSfeiyeFEgUOW+5++=XG4rT85Os4PNQ@mail.gmail.com>
2023-11-30 0:14 ` Bagas Sanjaya
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231129132527.8078-3-bagasdotme@gmail.com \
--to=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=jikos@kernel.org \
--cc=joe.lawrence@redhat.com \
--cc=jpoimboe@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=pmladek@suse.com \
--cc=tintinm2017@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.