From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Tomas Winkler <tomas.winkler@intel.com>
To: Alexander Usyskin <alexander.usyskin@intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Alexander Usyskin <alexander.usyskin@intel.com>
Cc: <stable@vger.kernel.org>
Cc: stable@vger.kernel.org
Subject: Re: [char-misc-next] mei: me: add cedar fork device ids
Date: Wed, 25 Mar 2020 01:02:01 +0000 [thread overview]
Message-ID: <20200325010201.DE8B62076F@mail.kernel.org> (raw)
In-Reply-To: <20200324210730.17672-1-tomas.winkler@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.11, v5.4.27, v4.19.112, v4.14.174, v4.9.217, v4.4.217.
v5.5.11: Build OK!
v5.4.27: Build OK!
v4.19.112: Build OK!
v4.14.174: Failed to apply! Possible dependencies:
1be8624a0cbe ("mei: me: add mule creek canyon (EHL) device ids")
4d86dfd38285 ("mei: me: add comet point (lake) LP device ids")
559e575a8946 ("mei: me: add comet point (lake) H device ids")
82b29b9f72af ("mei: me: add comet point V device id")
efe814e90b98 ("mei: me: add ice lake point device id.")
v4.9.217: Failed to apply! Possible dependencies:
1be8624a0cbe ("mei: me: add mule creek canyon (EHL) device ids")
4d86dfd38285 ("mei: me: add comet point (lake) LP device ids")
559e575a8946 ("mei: me: add comet point (lake) H device ids")
82b29b9f72af ("mei: me: add comet point V device id")
efe814e90b98 ("mei: me: add ice lake point device id.")
f8f4aa68a8ae ("mei: me: add cannon point device ids")
v4.4.217: Failed to apply! Possible dependencies:
1be8624a0cbe ("mei: me: add mule creek canyon (EHL) device ids")
4d86dfd38285 ("mei: me: add comet point (lake) LP device ids")
559e575a8946 ("mei: me: add comet point (lake) H device ids")
82b29b9f72af ("mei: me: add comet point V device id")
efe814e90b98 ("mei: me: add ice lake point device id.")
f8f4aa68a8ae ("mei: me: add cannon point device ids")
NOTE: The patch will not be queued to stable trees until it is upstream.
How should we proceed with this patch?
--
Thanks
Sasha
prev parent reply other threads:[~2020-03-25 1:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-24 21:07 [char-misc-next] mei: me: add cedar fork device ids Tomas Winkler
2020-03-25 1:02 ` 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=20200325010201.DE8B62076F@mail.kernel.org \
--to=sashal@kernel.org \
--cc=alexander.usyskin@intel.com \
/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).