The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Stephen Rothwell <sfr@canb.auug.org.au>
Subject: [GIT PULL] Driver core fixes for 5.7-rc5
Date: Fri, 8 May 2020 16:18:30 +0200	[thread overview]
Message-ID: <20200508141830.GA357188@kroah.com> (raw)

The following changes since commit 6a8b55ed4056ea5559ebe4f6a4b247f627870d4c:

  Linux 5.7-rc3 (2020-04-26 13:51:02 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git tags/driver-core-5.7-rc5

for you to fetch changes up to 2a15483b401c0b07e44b43b95414e36f32c02f32:

  regulator: Revert "Use driver_deferred_probe_timeout for regulator_init_complete_work" (2020-04-29 19:57:45 +0200)

----------------------------------------------------------------
Driver core fixes for 5.7-rc5

Here are a number of small driver core fixes for 5.7-rc5 to resolve a
bunch of reported issues with the current tree.

Biggest here are the reverts and patches from John Stultz to resolve a
bunch of deferred probe regressions we have been seeing in 5.7-rc right
now.

Along with those are some other smaller fixes:
	- coredump crash fix
	- devlink fix for when permissive mode was enabled
	- amba and platform device dma_parms fixes
	- component error silenced for when deferred probe happens

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

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

----------------------------------------------------------------
James Hilliard (1):
      component: Silence bind error on -EPROBE_DEFER

John Stultz (4):
      driver core: Revert default driver_deferred_probe_timeout value to 0
      driver core: Use dev_warn() instead of dev_WARN() for deferred_probe_timeout warnings
      driver core: Ensure wait_for_device_probe() waits until the deferred_probe_timeout fires
      regulator: Revert "Use driver_deferred_probe_timeout for regulator_init_complete_work"

Luis Chamberlain (1):
      coredump: fix crash when umh is disabled

Saravana Kannan (1):
      driver core: Fix handling of fw_devlink=permissive

Ulf Hansson (2):
      driver core: platform: Initialize dma_parms for platform devices
      amba: Initialize dma_parms for amba devices

 drivers/amba/bus.c              |  1 +
 drivers/base/component.c        |  8 +++++---
 drivers/base/core.c             |  7 ++++++-
 drivers/base/dd.c               | 20 ++++++++------------
 drivers/base/platform.c         |  2 ++
 drivers/regulator/core.c        | 25 +++++++++++--------------
 fs/coredump.c                   |  8 ++++++++
 include/linux/amba/bus.h        |  1 +
 include/linux/platform_device.h |  1 +
 kernel/umh.c                    |  5 +++++
 10 files changed, 48 insertions(+), 30 deletions(-)

             reply	other threads:[~2020-05-08 14:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-08 14:18 Greg KH [this message]
2020-05-08 16:15 ` [GIT PULL] Driver core fixes for 5.7-rc5 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=20200508141830.GA357188@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --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