mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alexander Shishkin <alexander.shishkin@linux.intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>
Subject: [GIT PULL v1 0/4] stm class/intel_th: Fixes for v5.3
Date: Wed, 21 Aug 2019 10:49:51 +0300	[thread overview]
Message-ID: <20190821074955.3925-1-alexander.shishkin@linux.intel.com> (raw)

Hi Greg,

These are the fixes that I have for v5.3. One is an actual bugfix that's
copied to stable, one SPDX header fix and two new PCI IDs, copied to
stable as well. Signed tag below, individual patches follow. Please
consider applying or pulling. Thanks!

Alexander Shishkin (2):
  intel_th: pci: Add support for another Lewisburg PCH
  intel_th: pci: Add Tiger Lake support

Ding Xiang (1):
  stm class: Fix a double free of stm_source_device

Nishad Kamdar (1):
  intel_th: Use the correct style for SPDX License Identifier

 drivers/hwtracing/intel_th/msu.h |  2 +-
 drivers/hwtracing/intel_th/pci.c | 10 ++++++++++
 drivers/hwtracing/intel_th/pti.h |  2 +-
 drivers/hwtracing/stm/core.c     |  1 -
 4 files changed, 12 insertions(+), 3 deletions(-)

-- 
2.23.0.rc1


             reply	other threads:[~2019-08-21  7:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-21  7:49 Alexander Shishkin [this message]
2019-08-21  7:49 ` [GIT PULL v1 1/4] stm class: Fix a double free of stm_source_device Alexander Shishkin
2019-08-21  7:49 ` [GIT PULL v1 2/4] intel_th: Use the correct style for SPDX License Identifier Alexander Shishkin
2019-08-21  7:49 ` [GIT PULL v1 3/4] intel_th: pci: Add support for another Lewisburg PCH Alexander Shishkin
2019-08-21  7:49 ` [GIT PULL v1 4/4] intel_th: pci: Add Tiger Lake support Alexander Shishkin
2019-08-28 15:24 ` [GIT PULL v1 0/4] stm class/intel_th: Fixes for v5.3 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=20190821074955.3925-1-alexander.shishkin@linux.intel.com \
    --to=alexander.shishkin@linux.intel.com \
    --cc=gregkh@linuxfoundation.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

all inboxes | Powered by JetHome®