[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAMB6jUGEJeOVKUEpeFosBFA3QsQk3kgdt_e1EAQJi_yqJp7H-A@mail.gmail.com>
Date: Mon, 27 Oct 2025 14:04:18 +0530
From: ally heev <allyheev@...il.com>
To: Dan Carpenter <dan.carpenter@...aro.org>
Cc: 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>,
dan.j.williams@...el.com
Subject: Re: [PATCH v2 2/2] add check for pointers with __free attribute
initialized to NULL
On Mon, Oct 27, 2025 at 10:57 AM Dan Carpenter <dan.carpenter@...aro.org> wrote:
> > General question about the process for my understanding:
> > Is checkpatch run on full tree by CI or someone and results reported
> > regularly ?
>
> Newbies run it regularly. Otherwise it gets run on subsystem CIs and
> the zero-day bot runs it on new patches but it will report the old
> warnings as well under the "Old warnings" section.
>
> > My understanding was that we would run it only on patches
> > before submitting them Or we just run it on full tree before adding
> > new checks to understand if they are catching real issues
>
> Eventually someone will look at all the warnings. And probably it's
> going to be a newbie and so we need to be careful with warning where
> newbies might introduce bugs with their changes.
>
> regards,
> dan carpenter
>
Makes sense. Thanks!!
---
aheev
Powered by blists - more mailing lists