linux-kernel - Re: [PATCH v3] MIPS: Fix MAX_REG

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.2504280235440.31828@angie.orcam.me.uk>
Date: Mon, 28 Apr 2025 02:43:50 +0100 (BST)
From: "Maciej W. Rozycki" <macro@...am.me.uk>
To: Huacai Chen <chenhuacai@...nel.org>
cc: Thomas Bogendoerfer <tsbogend@...ha.franken.de>, 
    Thorsten Blum <thorsten.blum@...ux.dev>, Oleg Nesterov <oleg@...hat.com>, 
    linux-mips@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3] MIPS: Fix MAX_REG_OFFSET

On Sun, 27 Apr 2025, Huacai Chen wrote:

> > > There is no 80 columns limit now, so no new line needed here.
> >
> > but not forbidden to care about it. I still prefer this limit.
> Of course you are free to choose. But in my opinion "force to long
> lines" and "force to short lines" are both bad, code readability is
> the first thing to be considered.

 Correct, and I start getting lost when lines are wrapped by overrunning 
the width of my screen.  NB in the old days some terminals would actually 
truncate lines instead; at least it does not happen anymore, or at least 
you can tell your terminal not to do it via a suitable stty(1) invocation.

  Maciej