linux-kernel - Re: [PATCH] Documentation/livepatch: Update terminology in livepatch

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

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