[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aPo1JU7pe-vvQzEf@stanley.mountain>
Date: Thu, 23 Oct 2025 17:01:09 +0300
From: Dan Carpenter <dan.carpenter@...aro.org>
To: ally heev <allyheev@...il.com>
Cc: dan.j.williams@...el.com, Dwaipayan Ray <dwaipayanray1@...il.com>,
Lukas Bulwahn <lukas.bulwahn@...il.com>,
Joe Perches <joe@...ches.com>, Jonathan Corbet <corbet@....net>,
Andy Whitcroft <apw@...onical.com>, workflows@...r.kernel.org,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
David Hunter <david.hunter.linux@...il.com>,
Shuah Khan <skhan@...uxfoundation.org>,
Viresh Kumar <vireshk@...nel.org>, Nishanth Menon <nm@...com>,
Stephen Boyd <sboyd@...nel.org>,
linux-pm <linux-pm@...r.kernel.org>
Subject: Re: [PATCH] checkpatch: add uninitialized pointer with __free
attribute check
On Thu, Oct 23, 2025 at 04:38:43PM +0530, ally heev wrote:
> I will take this back. Found this in `include/linux/cleanup.h`
> ```
> * Given that the "__free(...) = NULL" pattern for variables defined at
> * the top of the function poses this potential interdependency problem
> * the recommendation is to always define and assign variables in one
> * statement and not group variable definitions at the top of the
> * function when __free() is used.
> ```
Ah, right.
regards,
dan carpenter
Powered by blists - more mailing lists