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.8-rc6
Date: Thu, 16 Jul 2020 17:30:03 +0200 [thread overview]
Message-ID: <20200716153003.GA2379010@kroah.com> (raw)
The following changes since commit 9ebcfadb0610322ac537dd7aa5d9cbc2b2894c68:
Linux 5.8-rc3 (2020-06-28 15:00:24 -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.8-rc6
for you to fetch changes up to 2451e746478a6a6e981cfa66b62b791ca93b90c8:
driver core: Avoid deferred probe due to fw_devlink_pause/resume() (2020-07-10 15:20:38 +0200)
----------------------------------------------------------------
Driver core fixes for 5.8-rc6
Here are 3 driver core fixes for 5.8-rc6.
They resolve some issues found with the deferred probe code for some
types of devices on some embedded systems. They have been tested a
bunch and have been in linux-next for a while with no reported issues.
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
----------------------------------------------------------------
Saravana Kannan (3):
driver core: Don't do deferred probe in parallel with kernel_init thread
driver core: Rename dev_links_info.defer_sync to defer_hook
driver core: Avoid deferred probe due to fw_devlink_pause/resume()
drivers/base/base.h | 1 -
drivers/base/core.c | 44 ++++++++++++++++++++++++++++++++------------
drivers/base/dd.c | 5 -----
include/linux/device.h | 5 +++--
4 files changed, 35 insertions(+), 20 deletions(-)
next reply other threads:[~2020-07-16 15:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-16 15:30 Greg KH [this message]
2020-07-16 19:05 ` [GIT PULL] Driver core fixes for 5.8-rc6 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=20200716153003.GA2379010@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.