public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexander Shishkin <alexander.shishkin@linux.intel.com>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>
Subject: [PATCH v2 0/5] stm/intel_th: Updates for v4.4
Date: Wed, 25 Nov 2015 14:34:30 +0200	[thread overview]
Message-ID: <1448454875-21189-1-git-send-email-alexander.shishkin@linux.intel.com> (raw)

Hi Greg,

Since [1] hasn't yet found its way to char-misc tree, I'm re-sending
it with a few additions, namely: there is one more Kconfig fix from
Arnd and two PCI IDs that I'm hoping we could also include in this
cycle. Based on char-misc-linus.

[1] http://marc.info/?l=linux-kernel&m=144706387705997

Alexander Shishkin (2):
  intel_th: pci: Add Apollo Lake SOC support
  intel_th: pci: Add Broxton SOC support

Arnd Bergmann (1):
  stm: select CONFIG_SRCU

Geert Uytterhoeven (2):
  stm class: Hide STM-specific options if STM is disabled
  intel_th: INTEL_TH should depend on HAS_DMA

 drivers/hwtracing/intel_th/Kconfig |  1 +
 drivers/hwtracing/intel_th/pci.c   | 10 ++++++++++
 drivers/hwtracing/stm/Kconfig      |  5 +++++
 3 files changed, 16 insertions(+)

-- 
2.6.2


             reply	other threads:[~2015-11-25 12:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-25 12:34 Alexander Shishkin [this message]
2015-11-25 12:34 ` [PATCH v2 1/5] stm class: Hide STM-specific options if STM is disabled Alexander Shishkin
2015-11-25 12:34 ` [PATCH v2 2/5] intel_th: INTEL_TH should depend on HAS_DMA Alexander Shishkin
2015-11-25 12:34 ` [PATCH v2 3/5] stm: select CONFIG_SRCU Alexander Shishkin
2015-11-25 12:34 ` [PATCH v2 4/5] intel_th: pci: Add Apollo Lake SOC support Alexander Shishkin
2015-11-25 12:34 ` [PATCH v2 5/5] intel_th: pci: Add Broxton " 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=1448454875-21189-1-git-send-email-alexander.shishkin@linux.intel.com \
    --to=alexander.shishkin@linux.intel.com \
    --cc=greg@kroah.com \
    --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