From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Alexander Shishkin <alexander.shishkin@linux.intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org
Cc: stable@vger.kernel.org
Cc: stable@vger.kernel.org
Subject: Re: [GIT PULL 6/6] intel_th: pci: Add Elkhart Lake CPU support
Date: Tue, 17 Mar 2020 22:30:20 +0000 [thread overview]
Message-ID: <20200317223021.7720620409@mail.kernel.org> (raw)
In-Reply-To: <20200317062215.15598-7-alexander.shishkin@linux.intel.com>
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: v5.5.9, v5.4.25, v4.19.109, v4.14.173, v4.9.216, v4.4.216.
v5.5.9: Build OK!
v5.4.25: Build OK!
v4.19.109: Build OK!
v4.14.173: Build OK!
v4.9.216: Failed to apply! Possible dependencies:
4aa5aed2b6f2 ("intel_th: pci: Add Ice Lake NNPI support")
59d08d00d43c ("intel_th: pci: Add Ice Lake PCH support")
88385866bab8 ("intel_th: pci: Add Elkhart Lake SOC support")
920ce7c33db2 ("intel_th: pci: Add Cedar Fork PCH support")
9c78255fdde4 ("intel_th: pci: Add Tiger Lake support")
9d55499d8da4 ("intel_th: pci: Add Jasper Lake PCH support")
e60e9a4b231a ("intel_th: pci: Add Comet Lake support")
v4.4.216: Failed to apply! Possible dependencies:
4aa5aed2b6f2 ("intel_th: pci: Add Ice Lake NNPI support")
59d08d00d43c ("intel_th: pci: Add Ice Lake PCH support")
88385866bab8 ("intel_th: pci: Add Elkhart Lake SOC support")
920ce7c33db2 ("intel_th: pci: Add Cedar Fork PCH support")
9c78255fdde4 ("intel_th: pci: Add Tiger Lake support")
9d55499d8da4 ("intel_th: pci: Add Jasper Lake PCH support")
e60e9a4b231a ("intel_th: pci: Add Comet Lake support")
NOTE: The patch will not be queued to stable trees until it is upstream.
How should we proceed with this patch?
--
Thanks
Sasha
next prev parent reply other threads:[~2020-03-17 22:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200317062215.15598-1-alexander.shishkin@linux.intel.com>
2020-03-17 6:22 ` [GIT PULL 2/6] stm class: sys-t: Fix the use of time_after() Alexander Shishkin
2020-03-18 10:28 ` Greg Kroah-Hartman
2020-03-17 6:22 ` [GIT PULL 4/6] intel_th: msu: Fix the unexpected state warning Alexander Shishkin
2020-03-18 10:30 ` Greg Kroah-Hartman
2020-03-17 6:22 ` [GIT PULL 5/6] intel_th: Fix user-visible error codes Alexander Shishkin
2020-03-18 10:31 ` Greg Kroah-Hartman
2020-03-17 6:22 ` [GIT PULL 6/6] intel_th: pci: Add Elkhart Lake CPU support Alexander Shishkin
2020-03-17 22:30 ` Sasha Levin [this message]
2020-03-18 10:31 ` Greg Kroah-Hartman
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=20200317223021.7720620409@mail.kernel.org \
--to=sashal@kernel.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).