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 0/2] stm class/intel_th: Fixes for v4.17
Date: Thu, 24 May 2018 11:27:25 +0300 [thread overview]
Message-ID: <20180524082727.28990-1-alexander.shishkin@linux.intel.com> (raw)
Hi Greg,
These are 2 fixes I have for this release cycle, pretty straightforward.
Static checkers approve. Individual patches follow. Please consider pulling
or applying. Thanks!
The following changes since commit 60cc43fc888428bb2f18f08997432d426a243338:
Linux 4.17-rc1 (2018-04-15 18:24:20 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/ash/stm.git tags/stm-intel_th-fixes-for-greg-20180524
for you to fetch changes up to 3ce35db3ff05400e5676d0155cf261cc6bd3d351:
intel_th: Use correct device when freeing buffers (2018-05-24 10:55:03 +0300)
----------------------------------------------------------------
stm class/intel_th: Fixes for v4.17-rc1
These are 2 fixes, both backportable to stable:
* stm master array allocation moved to vmalloc
* intel_th/msu dma buffer deallocation fix.
----------------------------------------------------------------
Alexander Shishkin (2):
stm class: Use vmalloc for the master map
intel_th: Use correct device when freeing buffers
drivers/hwtracing/intel_th/msu.c | 6 +++---
drivers/hwtracing/stm/core.c | 6 +++---
2 files changed, 6 insertions(+), 6 deletions(-)
--
2.17.0
next reply other threads:[~2018-05-24 8:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-24 8:27 Alexander Shishkin [this message]
2018-05-24 8:27 ` [GIT PULL 1/2] stm class: Use vmalloc for the master map Alexander Shishkin
2018-05-24 8:27 ` [GIT PULL 2/2] intel_th: Use correct device when freeing buffers 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=20180524082727.28990-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®