From: Alexander Shishkin <alexander.shishkin@linux.intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Mathieu Poirier <mathieu.poirier@linaro.org>,
linux-kernel@vger.kernel.org,
Alexander Shishkin <alexander.shishkin@linux.intel.com>
Subject: [GIT PULL v1 0/7] stm class/intel_th: Updates for v5.1
Date: Thu, 21 Feb 2019 17:49:59 +0200 [thread overview]
Message-ID: <20190221155006.76832-1-alexander.shishkin@linux.intel.com> (raw)
Hi Greg,
Second attempt. Added stable CC and Fixes tags to fixes.
Here are the STM and Intel TH changes that I have for v5.1. Nothing big,
a few fixes that are too late for the v5.0 and a few minor cleanups and
a documentation update. All sparse/smatch/coccinelle/cppcheck/checkpatch
clean as usual, courtesy of aiaiai.
Individual patches follow. Please consider pulling or applying. Thanks!
The following changes since commit bfeffd155283772bbe78c6a05dec7c0128ee500c:
Linux 5.0-rc1 (2019-01-06 17:08:20 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/ash/stm.git tags/intel_th-stm-for-greg-20190221
for you to fetch changes up to 4c3cef46a96e8f623d1edf03424880ebc901b068:
stm class: Prevent division by zero (2019-02-21 15:29:26 +0200)
----------------------------------------------------------------
stm class/intel_th: Updates for v5.1
These are:
* 2 bugfixes in stm class
* one bugfix in intel_th
* a few minor cleanups
----------------------------------------------------------------
Alexander Shishkin (4):
intel_th: Update ABI documentation
intel_th: Only create useful device nodes
intel_th: Don't reference unassigned outputs
stm class: Prevent division by zero
Andy Shevchenko (1):
intel_th: pti: Use sysfs_match_string() helper
Gustavo A. R. Silva (1):
intel_th: Mark expected switch fall-throughs
Zhi Jin (1):
stm class: Fix an endless loop in channel allocation
.../testing/sysfs-bus-intel_th-output-devices | 6 ++++--
drivers/hwtracing/intel_th/core.c | 6 +++++-
drivers/hwtracing/intel_th/gth.c | 4 ++++
drivers/hwtracing/intel_th/pti.c | 16 +++++++---------
drivers/hwtracing/intel_th/sth.c | 4 ++++
drivers/hwtracing/stm/core.c | 11 ++++++++---
6 files changed, 32 insertions(+), 15 deletions(-)
--
2.20.1
next reply other threads:[~2019-02-21 15:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-21 15:49 Alexander Shishkin [this message]
2019-02-21 15:50 ` [GIT PULL v1 1/7] intel_th: Update ABI documentation Alexander Shishkin
2019-02-21 15:50 ` [GIT PULL v1 2/7] intel_th: Mark expected switch fall-throughs Alexander Shishkin
2019-02-21 15:50 ` [GIT PULL v1 3/7] intel_th: Only create useful device nodes Alexander Shishkin
2019-02-21 15:50 ` [GIT PULL v1 4/7] intel_th: pti: Use sysfs_match_string() helper Alexander Shishkin
2019-02-21 15:50 ` [GIT PULL v1 5/7] intel_th: Don't reference unassigned outputs Alexander Shishkin
2019-02-21 15:50 ` [GIT PULL v1 6/7] stm class: Fix an endless loop in channel allocation Alexander Shishkin
2019-02-21 15:50 ` [GIT PULL v1 7/7] stm class: Prevent division by zero Alexander Shishkin
2019-02-21 16:13 ` [GIT PULL v1 0/7] stm class/intel_th: Updates for v5.1 Greg Kroah-Hartman
2019-03-01 8:12 ` 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=20190221155006.76832-1-alexander.shishkin@linux.intel.com \
--to=alexander.shishkin@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.poirier@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;
as well as URLs for NNTP newsgroup(s).