[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1531753695-10311-1-git-send-email-kamalesh@linux.vnet.ibm.com>
Date: Mon, 16 Jul 2018 20:38:15 +0530
From: Kamalesh Babulal <kamalesh@...ux.vnet.ibm.com>
To: live-patching@...r.kernel.org
Cc: Kamalesh Babulal <kamalesh@...ux.vnet.ibm.com>,
linux-kernel@...r.kernel.org, Josh Poimboeuf <jpoimboe@...hat.com>
Subject: [PATCH v2] doc: livepatch: fix minor typo/grammar in shadow-vars.txt
Fix the spelling of 'varibles' -> 'variables' and grammar
in shadows->vars.txt file.
Signed-off-by: Kamalesh Babulal <kamalesh@...ux.vnet.ibm.com>
Cc: Josh Poimboeuf <jpoimboe@...hat.com>
---
v2 changes:
- Fixed the grammar of the sentence as suggested by Josh
Documentation/livepatch/shadow-vars.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/livepatch/shadow-vars.txt b/Documentation/livepatch/shadow-vars.txt
index ecc09a7be5dd..ffbc117e46f0 100644
--- a/Documentation/livepatch/shadow-vars.txt
+++ b/Documentation/livepatch/shadow-vars.txt
@@ -150,7 +150,7 @@ 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
+require shadow variables for 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.
--
2.7.4
Powered by blists - more mailing lists