public inbox for linux-kernel@vger.kernel.org
 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-rc7 - take 2
Date: Sun, 7 Oct 2018 08:07:55 +0200	[thread overview]
Message-ID: <20181007060755.GA13996@kroah.com> (raw)

The following changes since commit 17b57b1883c1285f3d0dc2266e8f79286a7bef38:

  Linux 4.19-rc6 (2018-09-30 07:15:35 -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-rc7

for you to fetch changes up to eafa717bc145963c944bb0a64d16add683861b35:

  thunderbolt: Initialize after IOMMUs (2018-10-02 10:51:16 -0700)

----------------------------------------------------------------
Char/Misc fixes for 4.19-rc7

Here are 8 small fixes for some char/misc driver issues

Included here are:
	- fpga driver fixes
	- thunderbolt bugfixes
	- firmware core revert/fix
	- hv core fix
	- hv tool fix

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

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

----------------------------------------------------------------
Alan Tull (3):
      fpga: do not access region struct after fpga_region_unregister
      fpga: bridge: fix obvious function documentation error
      docs: fpga: document fpga manager flags

Bjorn Andersson (1):
      firmware: Always initialize the fw_priv list object

Dexuan Cui (1):
      Drivers: hv: vmbus: Use get/put_cpu() in vmbus_connect()

Mika Westerberg (2):
      thunderbolt: Do not handle ICM events after domain is stopped
      thunderbolt: Initialize after IOMMUs

Vitaly Kuznetsov (1):
      tools: hv: fcopy: set 'error' in case an unknown operation was requested

 Documentation/driver-api/fpga/fpga-mgr.rst |  5 +++
 drivers/base/firmware_loader/main.c        |  7 +++--
 drivers/fpga/dfl-fme-region.c              |  4 ++-
 drivers/fpga/fpga-bridge.c                 |  2 +-
 drivers/fpga/of-fpga-region.c              |  3 +-
 drivers/hv/connection.c                    |  8 +++--
 drivers/thunderbolt/icm.c                  | 49 ++++++++++++------------------
 drivers/thunderbolt/nhi.c                  |  2 +-
 include/linux/fpga/fpga-mgr.h              | 20 ++++++++----
 tools/hv/hv_fcopy_daemon.c                 |  1 +
 10 files changed, 57 insertions(+), 44 deletions(-)

                 reply	other threads:[~2018-10-07  6:08 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=20181007060755.GA13996@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