From: Petr Mladek <pmladek@suse.com>
To: Bhaskar Chowdhury <unixbhaskar@gmail.com>
Cc: jpoimboe@redhat.com, jikos@kernel.org, mbenes@suse.cz,
joe.lawrence@redhat.com, corbet@lwn.net,
live-patching@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, rdunlap@infradead.org
Subject: Re: [PATCH] docs: livepatch: Fix a typo in the file shadow-vars.rst
Date: Fri, 5 Mar 2021 10:01:46 +0100 [thread overview]
Message-ID: <YEHzevqbmZg8kZ+7@alley> (raw)
In-Reply-To: <20210305021720.21874-1-unixbhaskar@gmail.com>
On Fri 2021-03-05 07:47:20, Bhaskar Chowdhury wrote:
>
> s/ varibles/variables/
>
> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.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.
It might make sense to move the "In" to the next line. It sticks out
even more now.
Eitherway:
Reviewed-by: Petr Mladek <pmladek@suse.com>
Best Regards,
Petr
next prev parent reply other threads:[~2021-03-05 9:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-05 2:17 [PATCH] docs: livepatch: Fix a typo in the file shadow-vars.rst Bhaskar Chowdhury
2021-03-05 9:01 ` Petr Mladek [this message]
2021-03-05 9:55 ` Bhaskar Chowdhury
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=YEHzevqbmZg8kZ+7@alley \
--to=pmladek@suse.com \
--cc=corbet@lwn.net \
--cc=jikos@kernel.org \
--cc=joe.lawrence@redhat.com \
--cc=jpoimboe@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=rdunlap@infradead.org \
--cc=unixbhaskar@gmail.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