From: Miroslav Benes <mbenes@suse.cz>
To: Bhaskar Chowdhury <unixbhaskar@gmail.com>
Cc: jpoimboe@redhat.com, jikos@kernel.org, pmladek@suse.com,
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
Date: Thu, 25 Mar 2021 10:18:05 +0100 (CET) [thread overview]
Message-ID: <alpine.LSU.2.21.2103251015260.30447@pobox.suse.cz> (raw)
In-Reply-To: <YFxTxxOkQDr2rb/J@OpenSuse>
On Thu, 25 Mar 2021, Bhaskar Chowdhury wrote:
> On 10:05 Thu 25 Mar 2021, Miroslav Benes wrote:
> >Hi,
> >
> >On Thu, 25 Mar 2021, 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.
> >
> >you sent the same fix a couple of weeks ago and Jon applied it.
> >
> Ah..difficult to remember....thanks for reminding ..it seems I need to keep
> track ...which I don't do at this moment ...so the patch get duplicated ..
Well, you definitely should.
> So.do you have any better policy to keep track???
I do not send a large amount of typo fixes, so it is quite easy to keep
track of everything in my case. So please, just find something that suits
you.
Miroslav
next prev parent reply other threads:[~2021-03-25 9:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-25 6:56 Bhaskar Chowdhury
2021-03-25 9:05 ` Miroslav Benes
2021-03-25 9:11 ` Bhaskar Chowdhury
2021-03-25 9:18 ` Miroslav Benes [this message]
2021-03-25 13:43 ` Jonathan Corbet
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=alpine.LSU.2.21.2103251015260.30447@pobox.suse.cz \
--to=mbenes@suse.cz \
--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=pmladek@suse.com \
--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
all inboxes | Powered by JetHome®