[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20210305100923.3731-1-unixbhaskar@gmail.com>
Date: Fri, 5 Mar 2021 15:39:23 +0530
From: Bhaskar Chowdhury <unixbhaskar@...il.com>
To: jpoimboe@...hat.com, jikos@...nel.org, mbenes@...e.cz,
pmladek@...e.com, joe.lawrence@...hat.com, corbet@....net,
live-patching@...r.kernel.org, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org
Cc: rdunlap@...radead.org, Bhaskar Chowdhury <unixbhaskar@...il.com>
Subject: [PATCH V2] docs: livepatch: Fix a typo and remove the unnecessary gaps in a sentence
s/varibles/variables/
...and remove leading spaces from a sentence.
Signed-off-by: Bhaskar Chowdhury <unixbhaskar@...il.com>
---
Changes from V1:
Pter pointed out some awkward leading space in a sentence ,fixed it.
Documentation/livepatch/shadow-vars.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/livepatch/shadow-vars.rst b/Documentation/livepatch/shadow-vars.rst
index c05715aeafa4..2ee114a91a35 100644
--- a/Documentation/livepatch/shadow-vars.rst
+++ b/Documentation/livepatch/shadow-vars.rst
@@ -165,8 +165,8 @@ In-flight parent objects
Sometimes it may not be convenient or possible to allocate shadow
variables alongside their parent objects. Or a livepatch fix may
-require shadow varibles to only a subset of parent object instances. In
-these cases, the klp_shadow_get_or_alloc() call can be used to attach
+require shadow variables to only a subset of parent object instances.
+In these cases, the klp_shadow_get_or_alloc() call can be used to attach
shadow variables to parents already in-flight.
For commit 1d147bfa6429, a good spot to allocate a shadow spinlock is
--
2.20.1
Powered by blists - more mailing lists