[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LSU.2.21.2103250956530.30447@pobox.suse.cz>
Date: Thu, 25 Mar 2021 10:05:46 +0100 (CET)
From: Miroslav Benes <mbenes@...e.cz>
To: Bhaskar Chowdhury <unixbhaskar@...il.com>
cc: jpoimboe@...hat.com, jikos@...nel.org, pmladek@...e.com,
joe.lawrence@...hat.com, corbet@....net,
live-patching@...r.kernel.org, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, rdunlap@...radead.org
Subject: Re: [PATCH] docs: livepatch: Fix a typo
Hi,
On Thu, 25 Mar 2021, Bhaskar Chowdhury wrote:
>
> s/varibles/variables/
>
> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@...il.com>
> ---
> Documentation/livepatch/shadow-vars.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/livepatch/shadow-vars.rst b/Documentation/livepatch/shadow-vars.rst
> index c05715aeafa4..8464866d18ba 100644
> --- a/Documentation/livepatch/shadow-vars.rst
> +++ b/Documentation/livepatch/shadow-vars.rst
> @@ -165,7 +165,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 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.
you sent the same fix a couple of weeks ago and Jon applied it.
Miroslav
Powered by blists - more mailing lists