linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Arnd Bergmann <arnd@arndb.de>,
	linux-kernel@vger.kernel.org
Subject: [GIT PULL] Char/Misc driver fixes for 4.19-rc6
Date: Tue, 25 Sep 2018 16:23:44 +0200	[thread overview]
Message-ID: <20180925142344.GA26980@kroah.com> (raw)

[Yes, the oddity of sending a pull request to myself is not lost on me...]

The following changes since commit 11da3a7f84f19c26da6f86af878298694ede0804:

  Linux 4.19-rc3 (2018-09-09 17:26:43 -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.19-rc4

for you to fetch changes up to 422b3db2a5036add39a82425b1dd9fb6c96481e8:

  firmware: Fix security issue with request_firmware_into_buf() (2018-09-12 09:31:00 +0200)

----------------------------------------------------------------
Char/Misc driver fixes for 4.19-rc4

Here are a small handful of char/misc driver fixes for 4.19-rc4.

All of them are simple, resolving reported problems in a few drivers.
Full details are in the shortlog.

All of these have been in linux-next with no reported issues.

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

----------------------------------------------------------------
Alexander Usyskin (1):
      mei: ignore not found client in the enumeration

Bryant G. Ly (1):
      misc: ibmvsm: Fix wrong assignment of return code

Gustavo A. R. Silva (1):
      misc: hmc6352: fix potential Spectre v1

John Hubbard (1):
      mei: fix use-after-free in mei_cl_write

K. Y. Srinivasan (1):
      Tools: hv: Fix a bug in the key delete code

Minchan Kim (1):
      android: binder: fix the race mmap and alloc_new_buf_locked

Rishabh Bhatnagar (1):
      firmware: Fix security issue with request_firmware_into_buf()

Stephen Hemminger (1):
      vmbus: don't return values for uninitalized channels

Tomas Winkler (2):
      mei: bus: fix hw module get/put balance
      mei: bus: need to unlink client before freeing

Wei Yongjun (1):
      fpga: dfl: fme: fix return value check in in pr_mgmt_init()

 drivers/android/binder_alloc.c      | 43 ++++++++++++++++++++++++++++++-------
 drivers/base/firmware_loader/main.c | 30 +++++++++++++++-----------
 drivers/fpga/dfl-fme-pr.c           |  2 +-
 drivers/hv/vmbus_drv.c              |  3 +++
 drivers/misc/hmc6352.c              |  2 ++
 drivers/misc/ibmvmc.c               |  2 +-
 drivers/misc/mei/bus.c              | 12 +++++------
 drivers/misc/mei/client.c           |  2 +-
 drivers/misc/mei/hbm.c              |  9 +++++---
 tools/hv/hv_kvp_daemon.c            |  2 +-
 10 files changed, 73 insertions(+), 34 deletions(-)

             reply	other threads:[~2018-09-25 14:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-25 14:23 Greg KH [this message]
2018-09-25 14:54 ` [GIT PULL] Char/Misc driver fixes for 4.19-rc6 Greg KH
2018-09-25 15:31   ` Arnd Bergmann
2018-09-25 15:56     ` gregkh

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=20180925142344.GA26980@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;
as well as URLs for NNTP newsgroup(s).