[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87o7eg607d.fsf@meer.lwn.net>
Date: Sat, 23 Dec 2023 15:08:54 -0700
From: Jonathan Corbet <corbet@....net>
To: attreyee-muk <tintinm2017@...il.com>, jpoimboe@...nel.org,
jikos@...nel.org, mbenes@...e.cz, pmladek@...e.com,
joe.lawrence@...hat.com
Cc: attreyee-muk <tintinm2017@...il.com>, linux-kernel@...r.kernel.org,
linux-doc@...r.kernel.org, live-patching@...r.kernel.org
Subject: Re: [PATCH] Documentation/livepatch: Update terminology in livepatch
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?
Also, please wrap your changelogs to a reasonable line length.
Thanks,
jon
Powered by blists - more mailing lists