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 1/2] Documentation: livepatch: Correct "step on each other's toes" idiom
Date: Wed, 29 Nov 2023 20:25:26 +0700 [thread overview]
Message-ID: <20231129132527.8078-2-bagasdotme@gmail.com> (raw)
In-Reply-To: <20231129132527.8078-1-bagasdotme@gmail.com>
The idiom is written as "step over" instead, which means walking over
something [1]; although it should have meant getting involved (interfere)
in each other redirection method's effect [2], as implied in the
surrounding context.
Correct the idiom.
Link: https://idioms.thefreedictionary.com/step+over [1]
Link: https://dictionary.cambridge.org/dictionary/english/step-on-toes [2]
Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
---
I choose to keep the singular version of 'each other' since it refers to
individual redirection method (see [3] for grammatical explanation of why
it is the case ).
[3]: https://jakubmarian.com/each-others-vs-each-others-in-english/
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..000059b3cbde49 100644
--- a/Documentation/livepatch/livepatch.rst
+++ b/Documentation/livepatch/livepatch.rst
@@ -39,7 +39,7 @@ and livepatching:
are in any way modified.
All three approaches need to modify the existing code at runtime. Therefore
-they need to be aware of each other and not step over each other's toes.
+they need to be aware of each other and not step on each other's toes.
Most of these problems are solved by using the dynamic ftrace framework as
a base. A Kprobe is registered as a ftrace handler when the function entry
is probed, see CONFIG_KPROBES_ON_FTRACE. Also an alternative function from
--
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 ` Bagas Sanjaya [this message]
2023-11-29 13:25 ` [PATCH 2/2] Documentation: livepatch: Correct opposite of releasing locks Bagas Sanjaya
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-2-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox