linux-kernel - Re: [PATCH] docs: clarify and improve wording in memory-barriers.txt

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] [day] [month] [year] [list]

Message-ID: <87o6sgekz5.fsf@trenco.lwn.net>
Date: Fri, 15 Aug 2025 08:08:14 -0600
From: Jonathan Corbet <corbet@....net>
To: shiva teja sathi <shivateja769@...il.com>, paulmck@...nel.org
Cc: akiyks@...il.com, parri.andrea@...il.com, haakon.bugge@...cle.com,
 linux-kernel@...r.kernel.org, shiva teja <shivateja769@...il.com>
Subject: Re: [PATCH] docs: clarify and improve wording in memory-barriers.txt

shiva teja sathi <shivateja769@...il.com> writes:

> From: shiva teja <shivateja769@...il.com>
>
> Signed-off-by: shiva teja <shivateja769@...il.com>
> ---
>  Documentation/memory-barriers.txt | 6032 ++++++++++++++---------------
>  1 file changed, 3016 insertions(+), 3016 deletions(-)

Thanks for working to improve our documentation.  Unfortunately, nobody
will be able to review this patch.  To have your changes considered,
please:

- Provide a proper changelog describing the changes you have made

- Avoid adding the CLRF line endings.  We do not use those in the
  kernel, and they completely obscure the changes you have actually made
  in the diff.

Thanks,

jon