linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Finn Thain <fthain@linux-m68k.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
Date: Sat, 1 Jul 2023 09:04:31 +0200	[thread overview]
Message-ID: <2023070113-trimming-undecided-4923@gregkh> (raw)
In-Reply-To: <1f5b0227-dbf6-4294-8532-525b3e405dc2@linux-m68k.org>

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.

thanks,

greg k-h

  reply	other threads:[~2023-07-01  7:10 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-19  9:41 [PATCH] Documentation: Linux Contribution Maturity Model and the wider community Finn Thain
2023-06-19  9:55 ` Greg Kroah-Hartman
2023-06-20  3:48   ` Finn Thain
2023-06-20 13:00     ` James Bottomley
2023-06-19 11:32 ` James Bottomley
2023-06-20  3:50   ` Finn Thain
2023-06-20 22:52     ` [Tech-board-discuss] " James Bottomley
2023-06-19 19:42 ` Theodore Ts'o
2023-06-20  3:54   ` Finn Thain
2023-06-20 21:25     ` Theodore Ts'o
2023-06-21  1:51       ` Finn Thain
2023-06-21 12:41         ` Greg Kroah-Hartman
2023-06-22  7:02           ` Finn Thain
2023-06-22  7:10             ` Greg Kroah-Hartman
2023-06-22  7:24               ` Finn Thain
2023-06-22 17:39             ` Theodore Ts'o
2023-06-23  0:52               ` Finn Thain
2023-06-23  1:45                 ` [Tech-board-discuss] " Mark Brown
2023-06-21 14:08         ` Steven Rostedt
2023-06-21 22:48           ` Finn Thain
2023-07-01  1:46           ` Measurement, was " Finn Thain
2023-07-01  7:04             ` Greg Kroah-Hartman [this message]
2023-07-01 22:54               ` [Tech-board-discuss] Measurement, was " Finn Thain
2023-06-21 22:44         ` Finn Thain
2023-06-23  2:32         ` Matthew Wilcox
2023-06-19 19:49 ` Kees Cook
2023-06-20  3:54   ` Finn Thain

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2023070113-trimming-undecided-4923@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=fthain@linux-m68k.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=tech-board-discuss@lists.linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).