* Re: [PATCH v2] i2c: i801: blacklist Host Notify on HP EliteBook G3 850
[not found] <20180402123435.5587-1-jandryuk@gmail.com>
@ 2018-04-05 1:34 ` Sasha Levin
2018-04-05 7:09 ` Jean Delvare
0 siblings, 1 reply; 3+ messages in thread
From: Sasha Levin @ 2018-04-05 1:34 UTC (permalink / raw)
To: Sasha Levin, Jason Andryuk, Jean Delvare, Wolfram Sang
Cc: benjamin.tissoires@redhat.com, andyrtr@archlinux.org,
stable@vger.kernel.org
Hi Jason Andryuk.
[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)
The bot has tested the following trees: v4.15.15, v4.14.32, v4.9.92, v4.4.126,
v4.15.15: Build OK!
v4.14.32: Build OK!
v4.9.92: Build OK!
v4.4.126: Build failed! Errors:
drivers/i2c/busses/i2c-i801.c:916:22: error: ‘FEATURE_HOST_NOTIFY’ undeclared (first use in this function); did you mean ‘X86_FEATURE_HWP_NOTIFY’?
Please let us know if you'd like to have this patch included in a stable tree.
--
Thanks.
Sasha
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH v2] i2c: i801: blacklist Host Notify on HP EliteBook G3 850
2018-04-05 1:34 ` [PATCH v2] i2c: i801: blacklist Host Notify on HP EliteBook G3 850 Sasha Levin
@ 2018-04-05 7:09 ` Jean Delvare
2018-04-06 20:04 ` Sasha Levin
0 siblings, 1 reply; 3+ messages in thread
From: Jean Delvare @ 2018-04-05 7:09 UTC (permalink / raw)
To: Sasha Levin
Cc: Jason Andryuk, Wolfram Sang, benjamin.tissoires, andyrtr, stable
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?
> The bot has tested the following trees: v4.15.15, v4.14.32, v4.9.92, v4.4.126,
>
> v4.15.15: Build OK!
> v4.14.32: Build OK!
> v4.9.92: Build OK!
> v4.4.126: Build failed! Errors:
> drivers/i2c/busses/i2c-i801.c:916:22: error: ‘FEATURE_HOST_NOTIFY’ undeclared (first use in this function); did you mean ‘X86_FEATURE_HWP_NOTIFY’?
No. If FEATURE_HOST_NOTIFY is not defined, then the patch is not needed
in the first place.
> Please let us know if you'd like to have this patch included in a stable tree.
Yes, I think the next iteration of the patch should be tagged to stable
trees inclusion.
--
Jean Delvare
SUSE L3 Support
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH v2] i2c: i801: blacklist Host Notify on HP EliteBook G3 850
2018-04-05 7:09 ` Jean Delvare
@ 2018-04-06 20:04 ` Sasha Levin
0 siblings, 0 replies; 3+ messages in thread
From: Sasha Levin @ 2018-04-06 20:04 UTC (permalink / raw)
To: Jean Delvare
Cc: Jason Andryuk, Wolfram Sang, benjamin.tissoires@redhat.com,
andyrtr@archlinux.org, stable@vger.kernel.org
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2018-04-06 20:04 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <20180402123435.5587-1-jandryuk@gmail.com>
2018-04-05 1:34 ` [PATCH v2] i2c: i801: blacklist Host Notify on HP EliteBook G3 850 Sasha Levin
2018-04-05 7:09 ` Jean Delvare
2018-04-06 20:04 ` Sasha Levin
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox