From: Bhaskar Chowdhury Date: Fri, 5 Mar 2021 10:09:23 +0000 (+0530) Subject: docs: livepatch: Fix a typo and remove the unnecessary gaps in a sentence X-Git-Tag: v5.13-rc1~164^2~88 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=a5907065ac1ab5cbcceea2a9ac0c40c1bef255fa;p=thirdparty%2Fkernel%2Flinux.git 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 Acked-by: Joe Lawrence Acked-by: Petr Mladek Link: https://lore.kernel.org/r/20210305100923.3731-1-unixbhaskar@gmail.com [jc: performed suggested prepositional tweak] Signed-off-by: Jonathan Corbet --- diff --git a/Documentation/livepatch/shadow-vars.rst b/Documentation/livepatch/shadow-vars.rst index c05715aeafa4e..6a7d43a8787d8 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 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. For commit 1d147bfa6429, a good spot to allocate a shadow spinlock is