linux-kernel - Re: [PATCH 7/9] CodingStyle: new variable declaration placement rule

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: <b14bb569-7c5f-4833-822e-a46f3be80ba7@kernel.org>
Date: Wed, 7 Jan 2026 13:28:38 +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 7/9] CodingStyle: new variable declaration placement rule

On 09/05/2025 22:34, Alexey Dobriyan wrote:
>  
> +Variable declarations
> +---------------------
> +
> +Each variable is declared in the innermost scope possible
> +where ``for`` initialization clause counts as a scope as well.
> +
> +Inside specific scope each variable is declared as late as possible as if
> +declarations have "mass" and "fall down":
> +
> +.. code-block:: c
> +
> +	int f(void *priv)
> +	{
> +		struct xxx_obj *obj = to_xxx_obj(priv);
> +
> +		rcu_read_lock();
> +		int s_xxx = 0;

NAK, so silence won't be treated as agreement.



Best regards,
Krzysztof