From: Tomas Winkler <tomas.winkler@intel.com>
To: stable@vger.kernel.org, Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org,
Alexander Usyskin <alexander.usyskin@intel.com>,
Tomas Winkler <tomas.winkler@intel.com>
Subject: [stable 4.4 0/2 V2] missing mei device ids
Date: Sun, 27 Aug 2017 08:52:50 +0300 [thread overview]
Message-ID: <20170827055252.6224-1-tomas.winkler@intel.com> (raw)
Device ids that are missing in 4.4 stable
Tomas Winkler (2):
mei: me: add broxton pci device ids
mei: me: add lewisburg device ids
drivers/misc/mei/hw-me-regs.h | 8 ++++++++
drivers/misc/mei/pci-me.c | 4 ++++
2 files changed, 12 insertions(+)
--
2.9.5
next reply other threads:[~2017-08-27 5:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-27 5:52 Tomas Winkler [this message]
2017-08-27 5:52 ` [stable 4.4 1/2 V2] mei: me: add broxton pci device ids Tomas Winkler
2017-08-27 5:52 ` [stable 4.4 2/2 V2] mei: me: add lewisburg " Tomas Winkler
2017-08-27 7:25 ` [stable 4.4 0/2 V2] missing mei " 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=20170827055252.6224-1-tomas.winkler@intel.com \
--to=tomas.winkler@intel.com \
--cc=alexander.usyskin@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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