The following changes since commit 609488bc979f99f805f34e9a32c1e3b71179d10b:

  Linux 5.3-rc2 (2019-07-28 12:47:02 -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-rc4

for you to fetch changes up to 5511c0c309db4c526a6e9f8b2b8a1483771574bc:

  coresight: Fix DEBUG_LOCKS_WARN_ON for uninitialized attribute (2019-08-01 
20:51:34 +0200)

----------------------------------------------------------------
Char/misc fixes for 5.3-rc4

Here are some small char/misc driver fixes for 5.3-rc4.

Two of these are for the habanalabs driver for issues found when running
on a big-endian system (are they still alive?)  The others are tiny
fixes reported by people, and a MAINTAINERS update about the location of
the fpga development tree.

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

Signed-off-by: Greg Kroah-Hartman <[email protected]>

----------------------------------------------------------------
Ben Segal (2):
      habanalabs: fix F/W download in BE architecture
      habanalabs: fix host memory polling in BE architecture

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

Jean Delvare (1):
      nvmem: Use the same permissions for eeprom as for nvmem

Moritz Fischer (1):
      MAINTAINERS: Move linux-fpga tree to new location

Suzuki K Poulose (1):
      coresight: Fix DEBUG_LOCKS_WARN_ON for uninitialized attribute

 MAINTAINERS                                      |  2 +-
 drivers/hwtracing/coresight/coresight-etm-perf.c |  1 +
 drivers/misc/habanalabs/command_submission.c     |  2 +-
 drivers/misc/habanalabs/firmware_if.c            | 22 ++++------------------
 drivers/misc/habanalabs/goya/goya.c              |  5 +++--
 drivers/misc/habanalabs/habanalabs.h             | 16 ++++++++++++++--
 drivers/nvmem/nvmem-sysfs.c                      | 15 +++++++++++----
 7 files changed, 35 insertions(+), 28 deletions(-)

Reply via email to