From: Alexander Shishkin <alexander.shishkin@linux.intel.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, laurent.fert@intel.com,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Chunyan Zhang <zhang.chunyan@linaro.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>
Subject: [GIT PULL] intel_th: Fixes for char-misc-linus
Date: Wed, 15 Mar 2017 15:00:38 +0200 [thread overview]
Message-ID: <87bmt24rux.fsf@ashishki-desk.ger.corp.intel.com> (raw)
Hi Greg,
Here are my fixes for 4.11, please consider pulling. One is an actual
bugfix, two others are new PCI IDs. Thanks!
The following changes since commit 4495c08e84729385774601b5146d51d9e5849f81:
Linux 4.11-rc2 (2017-03-12 14:47:08 -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-20170315
for you to fetch changes up to 340837f985c2cb87ca0868d4aa9ce42b0fab3a21:
intel_th: pci: Add Gemini Lake support (2017-03-15 14:55:18 +0200)
----------------------------------------------------------------
intel_th: Fixes for 4.11
These are:
* fix for a module refcount leak
* two new PCI IDs
----------------------------------------------------------------
Alexander Shishkin (3):
intel_th: Don't leak module refcount on failure to activate
intel_th: pci: Add Denverton SOC support
intel_th: pci: Add Gemini Lake support
drivers/hwtracing/intel_th/core.c | 4 +++-
drivers/hwtracing/intel_th/pci.c | 10 ++++++++++
2 files changed, 13 insertions(+), 1 deletion(-)
next reply other threads:[~2017-03-15 13:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-15 13:00 Alexander Shishkin [this message]
2017-03-16 1:47 ` [GIT PULL] intel_th: Fixes for char-misc-linus Greg KH
-- strict thread matches above, loose matches on Subject: below --
2017-07-26 12:46 Alexander Shishkin
2017-07-26 14:39 ` Greg KH
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=87bmt24rux.fsf@ashishki-desk.ger.corp.intel.com \
--to=alexander.shishkin@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=laurent.fert@intel.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