From: Jean Delvare <jdelvare@suse.com>
To: Sasha Levin <Alexander.Levin@microsoft.com>,
Jason Andryuk <jandryuk@gmail.com>,
Wolfram Sang <wsa@the-dreams.de>
Cc: "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 v3] i2c: i801: blacklist Host Notify on HP EliteBook G3 850
Date: Tue, 10 Apr 2018 16:39:20 +0200 [thread overview]
Message-ID: <1523371160.7994.100.camel@suse.com> (raw)
In-Reply-To: <DM5PR2101MB103222440AEF1DD5AD9D9F1DFBBE0@DM5PR2101MB1032.namprd21.prod.outlook.com>
On mar., 2018-04-10 at 13:49 +0000, Sasha Levin wrote:
> Hi,
>
> [This is an automated email]
>
> This commit has been processed because it contains a -stable tag.
> The stable tag indicates that it's relevant for the following trees: all
>
> The bot has tested the following trees: v4.16.1, v4.15.16, v4.14.33, v4.9.93, v4.4.127.
>
> v4.16.1: Build OK!
> v4.15.16: Build OK!
> v4.14.33: Build OK!
> v4.9.93: Build OK!
> v4.4.127: Build failed! Errors:
> i2c-i801.c:918: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.
Nack. As stated somewhere else in this thread, odds are that this
blacklisting won't be needed after all.
--
Jean Delvare
SUSE L3 Support
prev parent reply other threads:[~2018-04-10 14:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180404225643.6b40782f@endymion>
2018-04-05 18:38 ` [PATCH v3] i2c: i801: blacklist Host Notify on HP EliteBook G3 850 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 [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=1523371160.7994.100.camel@suse.com \
--to=jdelvare@suse.com \
--cc=Alexander.Levin@microsoft.com \
--cc=andyrtr@archlinux.org \
--cc=benjamin.tissoires@redhat.com \
--cc=jandryuk@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox