From: Bhaskar Chowdhury <unixbhaskar@gmail.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: jpoimboe@redhat.com, jikos@kernel.org, mbenes@suse.cz,
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 V2] docs: livepatch: Fix a typo and remove the unnecessary gaps in a sentence
Date: Fri, 5 Mar 2021 19:07:21 +0530 [thread overview]
Message-ID: <YEI0EcR5G53IoYzb@Gentoo> (raw)
In-Reply-To: <20210305125600.GM2723601@casper.infradead.org>
[-- Attachment #1: Type: text/plain, Size: 871 bytes --]
On 12:56 Fri 05 Mar 2021, Matthew Wilcox wrote:
>On Fri, Mar 05, 2021 at 03:39:23PM +0530, Bhaskar Chowdhury wrote:
>> s/varibles/variables/
>>
>> ...and remove leading spaces from a sentence.
>
>What do you mean 'leading spaces'? Separating two sentences with
>one space or two is a matter of personal style, and we do not attempt
>to enforce a particular style in the kernel.
>
The spaces before the "In" .. nor I am imposing anything , it was peter caught
and told me that it is hanging ..move it to the next line ..so I did. ..
>> 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.
>
>wrong preposition, s/to/for/ ..where???
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-03-05 13:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-05 10:09 [PATCH V2] docs: livepatch: Fix a typo and remove the unnecessary gaps in a sentence Bhaskar Chowdhury
2021-03-05 12:56 ` Matthew Wilcox
2021-03-05 13:37 ` Bhaskar Chowdhury [this message]
2021-03-05 16:00 ` Joe Lawrence
2021-03-08 10:18 ` Petr Mladek
2021-03-09 0:26 ` 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=YEI0EcR5G53IoYzb@Gentoo \
--to=unixbhaskar@gmail.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=pmladek@suse.com \
--cc=rdunlap@infradead.org \
--cc=willy@infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.