linux-kernel - Re: Clarifying confusion of our variable placement rules caused by cleanup.h

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: <ff13a1753f2395ebfe4fe559958ae5af5b0b424b.camel@perches.com>
Date: Sun, 18 Jan 2026 11:52:42 -0800
From: Joe Perches <joe@...ches.com>
To: Dan Carpenter <dan.carpenter@...aro.org>, James Bottomley
	 <James.Bottomley@...senpartnership.com>
Cc: Steven Rostedt <rostedt@...dmis.org>, Alexey Dobriyan
 <adobriyan@...il.com>,  Andy Shevchenko <andriy.shevchenko@...el.com>,
 ksummit@...ts.linux.dev, Dan Williams <dan.j.williams@...el.com>, 
 linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: Clarifying confusion of our variable placement rules caused by
 cleanup.h

On Sun, 2026-01-18 at 22:33 +0300, Dan Carpenter wrote:
> If you're working across the entire kernel like I do then it's safest
> to assume Upside Down Christmas Tree is the rule.

It's still a silly rule.  Like James wrote: Foible.

I did about 10 years ago suggest a checkpatch test though:

https://lore.kernel.org/lkml/1478242438.1924.31.camel@perches.com/