From: Sasha Levin <Alexander.Levin@microsoft.com>
To: Jean Delvare <jdelvare@suse.de>
Cc: Jason Andryuk <jandryuk@gmail.com>,
Wolfram Sang <wsa@the-dreams.de>,
"benjamin.tissoires@redhat.com" <benjamin.tissoires@redhat.com>,
"andyrtr@archlinux.org" <andyrtr@archlinux.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH v2] i2c: i801: blacklist Host Notify on HP EliteBook G3 850
Date: Fri, 6 Apr 2018 20:04:55 +0000 [thread overview]
Message-ID: <20180406200453.GA2341@sasha-vm> (raw)
In-Reply-To: <20180405090943.15daca6b@endymion>
On Thu, Apr 05, 2018 at 09:09:43AM +0200, Jean Delvare wrote:
>On Thu, 5 Apr 2018 01:34:22 +0000, Sasha Levin wrote:
>> [This is an automated email]
>>
>> This commit has been processed by the -stable helper bot and determined
>> to be a high probability candidate for -stable trees. (score: 5.1557)
>
>I have to admit I am curious how a bot can determine that. What are the
>heuristics?
Things like code metrics, words in the commit message, files changed,
author, who reviewed/signed-off/etc.
See https://soarsmu.github.io/papers/icse12-patch.pdf for some academic
background :)
--
Thanks,
Sasha
prev parent reply other threads:[~2018-04-06 20:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-02 12:25 [PATCH] i2c: i801: blacklist Host Notify on HP EliteBook G3 850 Jason Andryuk
2018-04-02 12:34 ` [PATCH v2] " Jason Andryuk
2018-04-03 19:13 ` Andreas Radke
2018-04-04 12:55 ` Jason Andryuk
2018-04-04 14:02 ` Jean Delvare
2018-04-06 15:23 ` Andreas Radke
2018-04-04 20:56 ` Jean Delvare
2018-04-05 18:38 ` [PATCH v3] " Jason Andryuk
2018-04-10 7:38 ` Jean Delvare
2018-04-10 9:10 ` Wolfram Sang
2018-04-10 13:49 ` Sasha Levin
2018-04-10 14:39 ` Jean Delvare
2018-04-05 1:34 ` [PATCH v2] " Sasha Levin
2018-04-05 7:09 ` Jean Delvare
2018-04-06 20:04 ` Sasha Levin [this message]
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=20180406200453.GA2341@sasha-vm \
--to=alexander.levin@microsoft.com \
--cc=andyrtr@archlinux.org \
--cc=benjamin.tissoires@redhat.com \
--cc=jandryuk@gmail.com \
--cc=jdelvare@suse.de \
--cc=stable@vger.kernel.org \
--cc=wsa@the-dreams.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.