From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx2.suse.de ([195.135.220.15]:38591 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750853AbeDEHJr (ORCPT ); Thu, 5 Apr 2018 03:09:47 -0400 Date: Thu, 5 Apr 2018 09:09:43 +0200 From: Jean Delvare To: Sasha Levin Cc: Jason Andryuk , Wolfram Sang , benjamin.tissoires@redhat.com, andyrtr@archlinux.org, stable@vger.kernel.org Subject: Re: [PATCH v2] i2c: i801: blacklist Host Notify on HP EliteBook G3 850 Message-ID: <20180405090943.15daca6b@endymion> In-Reply-To: References: <20180402123435.5587-1-jandryuk@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT Sender: stable-owner@vger.kernel.org List-ID: 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