Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.37 as permitted sender) client-ip=23.128.96.37;
Message-ID: <202dbdf5-1adf-4ffa-a50d-0424967286ba@infradead.org>
Date:   Mon, 27 Nov 2023 11:41:31 -0800
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: [PATCH] Took care of some grammatical mistakes
Content-Language: en-US
To:     attreyee-muk <tintinm2017@gmail.com>, jpoimboe@kernel.org,
        jikos@kernel.org, mbenes@suse.cz, pmladek@suse.com,
        joe.lawrence@redhat.com, corbet@lwn.net
Cc:     live-patching@vger.kernel.org, linux-doc@vger.kernel.org,
        linux-kernel@vger.kernel.org
References: <20231127155758.33070-1-tintinm2017@gmail.com>
From:   Randy Dunlap <rdunlap@infradead.org>
In-Reply-To: <20231127155758.33070-1-tintinm2017@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: bulk

Hi,

On 11/27/23 07:57, attreyee-muk wrote:
> Respected Maintainers, 
> 
> I have made some grammatical changes in the livepatch.rst file where I
> felt that the sentence would have sounded more correct and would have become easy for
> beginners to understand by reading. 
> Requesting review of my proposed changes from the mainatiners. 
> 
> Thank You
> Attreyee Mukherjee
> 
> Signed-off-by: attreyee-muk <tintinm2017@gmail.com>
> ---
>  Documentation/livepatch/livepatch.rst | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/Documentation/livepatch/livepatch.rst b/Documentation/livepatch/livepatch.rst
> index 68e3651e8af9..a2d2317b7d6b 100644
> --- a/Documentation/livepatch/livepatch.rst
> +++ b/Documentation/livepatch/livepatch.rst
> @@ -35,11 +35,11 @@ and livepatching:
>  
>  All three approaches need to modify the existing code at runtime. Therefore
> -they need to be aware of each other and not step over each other's toes.
> +they need to be aware of each other and not step over each others' toes.

I've never seen that written like that, so I disagree here. FWIW.

>  Most of these problems are solved by using the dynamic ftrace framework as
>  a base. A Kprobe is registered as a ftrace handler when the function entry
>  is probed, see CONFIG_KPROBES_ON_FTRACE. Also an alternative function from

thanks.
-- 
~Randy