mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Arnd Bergmann <arnd@arndb.de>
Cc: linux-kernel@vger.kernel.org
Subject: [GIT PULL] Char/Misc driver fixes for 4.17-rc8
Date: Sat, 2 Jun 2018 14:35:17 +0200	[thread overview]
Message-ID: <20180602123517.GB15904@kroah.com> (raw)

The following changes since commit 6da6c0db5316275015e8cc2959f12a17584aeb64:

  Linux v4.17-rc3 (2018-04-29 14:17:42 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git/ tags/char-misc-4.17-rc8

for you to fetch changes up to 806e30873f0e74d9d41b0ef761bd4d3e55c7d510:

  hwtracing: stm: fix build error on some arches (2018-05-26 08:49:24 +0200)

----------------------------------------------------------------
Char/Misc driver fixes for 4.17-rc8

Here are 4 small bugfixes for some char/misc drivers.  Well, really 3
fixes and one fix for one of those fixes due to problems found by 0-day.

This resolves some reported issues with the hwtracing drivers, and a
reported regression for the thunderbolt subsystem.  All of these have
been in linux-next for a while now with no reported problems.

Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

----------------------------------------------------------------
Alexander Shishkin (2):
      stm class: Use vmalloc for the master map
      intel_th: Use correct device when freeing buffers

Greg Kroah-Hartman (1):
      hwtracing: stm: fix build error on some arches

Mika Westerberg (1):
      thunderbolt: Handle NULL boot ACL entries properly

 drivers/hwtracing/intel_th/msu.c | 6 +++---
 drivers/hwtracing/stm/core.c     | 7 ++++---
 drivers/thunderbolt/icm.c        | 2 +-
 3 files changed, 8 insertions(+), 7 deletions(-)

                 reply	other threads:[~2018-06-02 12:35 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20180602123517.GB15904@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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®