[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZYpb6Woh45ZnEvCP@archie.me>
Date: Tue, 26 Dec 2023 11:51:53 +0700
From: Bagas Sanjaya <bagasdotme@...il.com>
To: Jonathan Corbet <corbet@....net>, attreyee-muk <tintinm2017@...il.com>,
jpoimboe@...nel.org, jikos@...nel.org, mbenes@...e.cz,
pmladek@...e.com, joe.lawrence@...hat.com
Cc: linux-kernel@...r.kernel.org, linux-doc@...r.kernel.org,
live-patching@...r.kernel.org
Subject: Re: [PATCH] Documentation/livepatch: Update terminology in livepatch
On Sat, Dec 23, 2023 at 03:08:54PM -0700, Jonathan Corbet wrote:
> attreyee-muk <tintinm2017@...il.com> writes:
>
> > Update the sentence in livepatch.rst to: "Functions are there for a reason. Take some input parameters, acquire or release locks, read, process, and write some data in a defined way."
> >
> > Signed-off-by: Attreyee Mukherjee <tintinm2017@...il.com>
> > ---
> > Documentation/livepatch/livepatch.rst | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
>
> So this is a classic example of saying what you have done, but not why.
> What makes this a change that we want?
I think what he intended was "The word 'get' is not the correct antonym to
'release' in the context of locking. Replace it with 'acquire'".
Thanks.
--
An old man doll... just what I always wanted! - Clara
Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)
Powered by blists - more mailing lists