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:48:31 +0200 [thread overview]
Message-ID: <024171e5a6955e77a9a55a0088baa9ea@newmail.lip6.fr> (raw)
In-Reply-To: <20160826112635.GA27627@kroah.com>
Le 26.08.2016 13:26, Greg KH a écrit :
> On Fri, Aug 26, 2016 at 12:46:51AM -0400, Levin, Alexander wrote:
>> - Making checkpatch check for (some) of the stable kernel rules
>> (and possibly recommend adding the stable@ tag in certain cases?).
>> - Depends on: making checkpatch sane again.
>
> This sounds interesting. What do you mean by "sane"? "sane" as in
> rewriting it so that someone who isn't a perl master can modify it? Or
> "sane" as in "don't be so pedantic about things that don't matter"?
A few years ago, I did some work on automatically identifying bug fixing
patches, based on combining information from the log message and the
code. For example, one issue would be the number of changes in the
code, because a big change, even if it was a bug fix, might be too
complex for stable. Machine learning was involved. The obvious weak
point of the work was that we only had me to label the data, as opposed
to a real stable maintainer. If you think it could be useful to pursue
this work, and do a better job, and would be willing to help out in
creating the datasets, then perhaps it could be something to pursue
again. My collaborator on this work is David Lo of Singapore Management
University. I will be visiting him in the first week of September and
could discuss with him further. If by chance you think of something
else where machine learning could be relevant to kernel development, I
could bring that up as well. He knows everything about applying machine
learning to software development issues, but nothing about the Linux
kernel, or even C code.
julia
next prev parent reply other threads:[~2016-08-26 11:54 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 [this message]
2016-08-26 11:55 ` Julia Lawall
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=024171e5a6955e77a9a55a0088baa9ea@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