Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Feedback-ID: i58a146ae:Fastmail
Date:   Sun, 2 Jul 2023 08:54:28 +1000 (AEST)
From:   Finn Thain <fthain@linux-m68k.org>
To:     Greg Kroah-Hartman <gregkh@linuxfoundation.org>
cc:     Steven Rostedt <rostedt@goodmis.org>,
        tech-board-discuss@lists.linux-foundation.org,
        linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [Tech-board-discuss] Measurement, was Re: [PATCH] Documentation:
 Linux Contribution Maturity Model and the wider community
In-Reply-To: <2023070113-trimming-undecided-4923@gregkh>
Message-ID: <2b3c665e-331e-3262-5874-a2e6755f6b0e@linux-m68k.org>
References: <20230620212502.GI286961@mit.edu> <5490402b-8b9f-f52d-3896-41090e639e51@linux-m68k.org> <20230621100845.12588f48@gandalf.local.home> <1f5b0227-dbf6-4294-8532-525b3e405dc2@linux-m68k.org> <2023070113-trimming-undecided-4923@gregkh>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Precedence: bulk

On Sat, 1 Jul 2023, Greg Kroah-Hartman wrote:

> On Sat, Jul 01, 2023 at 11:46:18AM +1000, Finn Thain wrote:
> > BTW. I assume that 'Fixes' tags are already being used to train AI 
> > models to locate bugs in existing code. If this could be used to 
> > evaluate new patches when posted, it might make the code review 
> > process more efficient.
> 
> That has been happening for many many years now with papers being 
> published about it and many conference presentations.  It shouldn't be a 
> secret it's been happening and directly helping with stable kernel 
> maintenance for a long time.
> 

Many years ago it struck me that the deficiencies of checkpatch.pl could 
be addressed with coccinelle but I still don't see this happening on the 
lists I read.

I see reviewers being spared from having to examine many flawed patches 
because the zero-day bot intercepted them and fed them to static 
analyzers. But I still don't see coccinelle being used to the same end 
i.e. to reduce the burden on reviewers and maintainers.

Has no-one tried it, or did it not work out?