linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: attreyee-muk <tintinm2017@gmail.com>
To: jpoimboe@kernel.org, jikos@kernel.org, mbenes@suse.cz,
	pmladek@suse.com, joe.lawrence@redhat.com, corbet@lwn.net
Cc: attreyee-muk <tintinm2017@gmail.com>,
	live-patching@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH] Took care of some grammatical mistakes
Date: Mon, 27 Nov 2023 21:27:59 +0530	[thread overview]
Message-ID: <20231127155758.33070-1-tintinm2017@gmail.com> (raw)

Respected Maintainers, 

I have made some grammatical changes in the livepatch.rst file where I
felt that the sentence would have sounded more correct and would have become easy for
beginners to understand by reading. 
Requesting review of my proposed changes from the mainatiners. 

Thank You
Attreyee Mukherjee

Signed-off-by: attreyee-muk <tintinm2017@gmail.com>
---
 Documentation/livepatch/livepatch.rst | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/Documentation/livepatch/livepatch.rst b/Documentation/livepatch/livepatch.rst
index 68e3651e8af9..a2d2317b7d6b 100644
--- a/Documentation/livepatch/livepatch.rst
+++ b/Documentation/livepatch/livepatch.rst
@@ -35,11 +35,11 @@ and livepatching:
     compiler using the '-pg' gcc option.
 
   - Livepatching typically needs to redirect the code at the very beginning
-    of the function entry before the function parameters or the stack
+    of the function entry, before the function parameters or the stack
     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 over each others' 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
@@ -50,8 +50,8 @@ some limitations, see below.
 3. Consistency model
 ====================
 
-Functions are there for a reason. They take some input parameters, get or
-release locks, read, process, and even write some data in a defined way,
+Functions are there for a reason. They take some input parameters, acquire or
+release locks, read, process, write some data in a defined way, and also
 have return values. In other words, each function has a defined semantic.
 
 Many fixes do not change the semantic of the modified functions. For
-- 
2.34.1


             reply	other threads:[~2023-11-27 16:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-27 15:57 attreyee-muk [this message]
2023-11-27 16:47 ` [PATCH] Took care of some grammatical mistakes Jonathan Corbet
2023-11-27 19:41 ` Randy Dunlap
2023-11-28 14:12   ` Matthew Wilcox
2023-11-28 16:18     ` Randy Dunlap
2023-11-29 10:08       ` Miroslav Benes
2023-11-29 12:47         ` Bagas Sanjaya
2023-11-29 14:48         ` Joe Lawrence

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=20231127155758.33070-1-tintinm2017@gmail.com \
    --to=tintinm2017@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 \
    /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;
as well as URLs for NNTP newsgroup(s).