From: Alexander Shishkin <alexander.shishkin@linux.intel.com>
To: Greg KH <greg@kroah.com>
Cc: Mathieu Poirier <mathieu.poirier@linaro.org>,
Chunyan Zhang <zhang.chunyan@linaro.org>,
linux-kernel@vger.kernel.org,
Alexander Shishkin <alexander.shishkin@linux.intel.com>
Subject: [GIT PULL 0/3] intel_th/stm class: Fixes for v4.14
Date: Tue, 19 Sep 2017 18:47:39 +0300 [thread overview]
Message-ID: <20170919154742.19696-1-alexander.shishkin@linux.intel.com> (raw)
Hi Greg,
These are the fixes I have so far for v4.14 window: 2 new PCI IDs and
one actual fix. Please consider pulling and/or applying. Thanks!
The following changes since commit 2bd6bf03f4c1c59381d62c61d03f6cc3fe71f66e:
Linux 4.14-rc1 (2017-09-16 15:47:51 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/ash/stm.git tags/stm-fixes-for-greg-20170919
for you to fetch changes up to 4de8301b8cc7287585c93639934426388c6718c6:
intel_th: pci: Add Lewisburg PCH support (2017-09-19 18:32:10 +0300)
----------------------------------------------------------------
intel_th/stm class: Fixes for v4.14
These are:
* 2 new PCI IDs
* fix for stm_source device removal path
----------------------------------------------------------------
Alexander Shishkin (3):
stm class: Fix a use-after-free
intel_th: pci: Add Cedar Fork PCH support
intel_th: pci: Add Lewisburg PCH support
drivers/hwtracing/intel_th/pci.c | 10 ++++++++++
drivers/hwtracing/stm/core.c | 2 +-
2 files changed, 11 insertions(+), 1 deletion(-)
--
2.14.1
next reply other threads:[~2017-09-19 15:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-19 15:47 Alexander Shishkin [this message]
2017-09-19 15:47 ` [GIT PULL 1/3] stm class: Fix a use-after-free Alexander Shishkin
2017-09-22 8:28 ` Greg KH
2017-09-22 9:06 ` Alexander Shishkin
2017-09-19 15:47 ` [GIT PULL 2/3] intel_th: pci: Add Cedar Fork PCH support Alexander Shishkin
2017-09-19 15:47 ` [GIT PULL 3/3] intel_th: pci: Add Lewisburg " Alexander Shishkin
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=20170919154742.19696-1-alexander.shishkin@linux.intel.com \
--to=alexander.shishkin@linux.intel.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=zhang.chunyan@linaro.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