public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Arnd Bergmann <arnd@arndb.de>,
	linux-kernel@vger.kernel.org
Subject: [GIT PULL] Char/Misc driver fixes for 5.3-rc2
Date: Sun, 28 Jul 2019 14:01:55 +0200	[thread overview]
Message-ID: <20190728120155.GA16225@kroah.com> (raw)

The following changes since commit 5f9e832c137075045d15cd6899ab0505cfb2ca4b:

  Linus 5.3-rc1 (2019-07-21 14:05:38 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git tags/char-misc-5.3-rc2

for you to fetch changes up to d4fddac5a51c378c5d3e68658816c37132611e1f:

  test_firmware: fix a memory leak bug (2019-07-25 14:39:52 +0200)

----------------------------------------------------------------
Char/Misc driver fixes for 5.3-rc2

Here are some small char and misc driver fixes for 5.3-rc2 to resolve
some reported issues.

Nothing major at all, some binder bugfixes for issues found, some new
mei device ids, firmware building warning fixes, habanalabs fixes, a few
other build fixes, and a MAINTAINERS update.

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: me: add mule creek canyon (EHL) device ids

Arnd Bergmann (1):
      habanalabs: use %pad for printing a dma_addr_t

Arseny Solokha (1):
      eeprom: make older eeprom drivers select NVMEM_SYSFS

Greg Kroah-Hartman (1):
      Merge tag 'misc-habanalabs-fixes-2019-07-22' of git://people.freedesktop.org/~gabbayo/linux into char-misc-linux

Hridya Valsaraju (1):
      binder: prevent transactions to context manager from its own process.

Kefeng Wang (1):
      hpet: Fix division by zero in hpet_time_div()

Martijn Coenen (1):
      binder: Set end of SG buffer area properly.

Mauro Rossi (1):
      firmware: fix build errors in paged buffer handling code

Nadav Amit (1):
      vmw_balloon: Remove Julien from the maintainers list

Oded Gabbay (1):
      habanalabs: don't reset device when getting VRHOT

Takashi Iwai (1):
      firmware: Fix missing inline

Wenwen Wang (1):
      test_firmware: fix a memory leak bug

YueHaibing (1):
      fpga-manager: altera-ps-spi: Fix build error

 MAINTAINERS                             | 1 -
 drivers/android/binder.c                | 5 +++--
 drivers/base/firmware_loader/firmware.h | 4 ++--
 drivers/char/hpet.c                     | 3 +--
 drivers/fpga/Kconfig                    | 1 +
 drivers/misc/eeprom/Kconfig             | 3 +++
 drivers/misc/habanalabs/goya/goya.c     | 6 +++---
 drivers/misc/mei/hw-me-regs.h           | 3 +++
 drivers/misc/mei/pci-me.c               | 3 +++
 lib/test_firmware.c                     | 5 ++++-
 10 files changed, 23 insertions(+), 11 deletions(-)

             reply	other threads:[~2019-07-28 12:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-28 12:01 Greg KH [this message]
2019-07-28 17:30 ` [GIT PULL] Char/Misc driver fixes for 5.3-rc2 pr-tracker-bot

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=20190728120155.GA16225@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