ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Julia Lawall <Julia.Lawall@lip6.fr>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: ksummit-discuss@lists.linuxfoundation.org, "Levin,
	Alexander" <alexander.levin@verizon.com>
Subject: Re: [Ksummit-discuss] Self nomination - Sasha Levin
Date: Fri, 26 Aug 2016 13:55:27 +0200	[thread overview]
Message-ID: <cfea840fae5911cdff7fbad535e9261b@newmail.lip6.fr> (raw)
In-Reply-To: <20160826112635.GA27627@kroah.com>

Not sure if I was clear about what I was asking you to agree to :)

Basically, we can take the patches sent to stable and the patches not 
sent to stable as a training set, but then the machine learning comes up 
with some algorithm that produces some results.  An expert is needed to 
evaluate the results.  Ie for a thousand (number chosen at random) 
patches, if the algorithm says it is a bug fixing patch, is it or isn't 
it, and vice versa.  Of course, we could also evaluate on patches that 
previously have and have not been sent too stable, but there is a 
problem there, because our goal is to have more patches sent to stable 
than are already being sent there, so we need to show that the algorithm 
can capture what humans are missing.

julia

  parent reply	other threads:[~2016-08-26 11:55 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-26  4:46 Levin, Alexander
2016-08-26 11:26 ` Greg KH
2016-08-26 11:42   ` James Hogan
2016-08-26 11:50     ` James Hogan
2016-08-26 12:27       ` Jani Nikula
2016-08-26 12:39         ` James Hogan
2016-08-26 11:56     ` Greg KH
2016-08-26 12:17       ` James Hogan
2016-08-26 13:44       ` Levin, Alexander
2016-08-26 11:48   ` Julia Lawall
2016-08-26 11:55   ` Julia Lawall [this message]
2016-08-26 12:11     ` Greg KH
2016-08-26 13:51       ` Levin, Alexander
2016-08-26 13:55         ` Julia Lawall
2016-08-26 18:52           ` Levin, Alexander
2016-08-26 19:59             ` Julia Lawall
2016-08-26 12:08   ` Julia Lawall
2016-08-26 18:55     ` Levin, Alexander
2016-08-26 13:39   ` Levin, Alexander

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=cfea840fae5911cdff7fbad535e9261b@newmail.lip6.fr \
    --to=julia.lawall@lip6.fr \
    --cc=alexander.levin@verizon.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=ksummit-discuss@lists.linuxfoundation.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