linux-kernel - Re: [PATCH 9/9] CodingStyle: flip the rule about curlies

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: <8ac45a1f-df9c-4e41-bf44-a1a6d4b41042@kernel.org>
Date: Wed, 7 Jan 2026 13:32:45 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Alexey Dobriyan <adobriyan@...il.com>, corbet@....net
Cc: workflows@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 9/9] CodingStyle: flip the rule about curlies

On 07/01/2026 13:29, Krzysztof Kozlowski wrote:
> On 09/05/2025 22:34, Alexey Dobriyan wrote:
>> Require set of curlies {} in all if/else branches and all loops
>> not matter how simple.
>>
>> The rationale is that maintaining curlies increases churn and make
>> patches bigger when those if/else branches grow and shrink so it is
>> easier to always add them.
>>
>> There are more important things in life than herding curlies.
> 
> 
> NAK, so silence won't be treated as agreement.

... and I failed to notice that this thread was dug up by one person and
it is way forgotten. Sorry for the noise.

Best regards,
Krzysztof