linux-kernel - Re: [PATCH 1/1] alpha: trivial: remove ^L chars

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]

Message-ID: <alpine.DEB.2.21.2601061310110.45251@angie.orcam.me.uk>
Date: Tue, 6 Jan 2026 13:17:57 +0000 (GMT)
From: "Maciej W. Rozycki" <macro@...am.me.uk>
To: Magnus Lindholm <linmag7@...il.com>
cc: Askar Safin <safinaskar@...il.com>, 
    Richard Henderson <richard.henderson@...aro.org>, 
    Matt Turner <mattst88@...il.com>, linux-alpha@...r.kernel.org, 
    kernel-janitors@...r.kernel.org, linux-kernel@...r.kernel.org, 
    patches@...ts.linux.dev
Subject: Re: [PATCH 1/1] alpha: trivial: remove ^L chars

On Mon, 5 Jan 2026, Magnus Lindholm wrote:

> For a v2, please consider adjusting the commit message rationale away from
> personal tooling and towards general readability and editor/tool compatibility.

 As a matter of interest, why would the presence of ^L characters cause 
any issues?  That is just another instance of white space and it has been 
commonly used across some source code to separate functional parts, e.g. 
in the GNU toolchain.  It can be ignored unless you actually send the code 
to a printer (which I suppose hardly anyone does nowadays).

  Maciej