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.11-rc5
Date: Sun, 24 Jan 2021 13:58:32 +0100 [thread overview]
Message-ID: <YA1u+IPixwAx6t7P@kroah.com> (raw)
The following changes since commit e71ba9452f0b5b2e8dc8aa5445198cd9214a6a62:
Linux 5.11-rc2 (2021-01-03 15:55:30 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git tags/driver-core-5.11-rc5
for you to fetch changes up to e020ff611ba9be54e959e6b548038f8a020da1c9:
driver core: Fix device link device name collision (2021-01-21 20:12:40 +0100)
----------------------------------------------------------------
Driver core fixes for 5.11-rc5
Here are some small driver core fixes for 5.11-rc5 that resolve some
reported problems:
- revert of a -rc1 patch that was causing problems with some
machines
- device link device name collision problem fix (busses only
have to name devices unique to their bus, not unique to all
busses)
- kernfs splice bugfixes to resolve firmware loading problems
for Qualcomm systems.
- other tiny driver core fixes for minor issues reported.
All of these have been in linux-next with no reported problems.
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
----------------------------------------------------------------
Christoph Hellwig (3):
kernfs: implement ->read_iter
kernfs: implement ->write_iter
kernfs: wire up ->splice_read and ->splice_write
Greg Kroah-Hartman (1):
Revert "driver core: Reorder devices on successful probe"
John Garry (1):
Driver core: platform: Add extra error check in devm_platform_get_irqs_affinity()
Meng Li (1):
drivers core: Free dma_range_map when driver probe failed
Rafael J. Wysocki (1):
driver core: Extend device_is_dependent()
Saravana Kannan (1):
driver core: Fix device link device name collision
Documentation/ABI/testing/sysfs-class-devlink | 4 +-
Documentation/ABI/testing/sysfs-devices-consumer | 5 +-
Documentation/ABI/testing/sysfs-devices-supplier | 5 +-
drivers/base/core.c | 44 +++++++++++-----
drivers/base/dd.c | 9 +---
drivers/base/platform.c | 2 +
fs/kernfs/file.c | 65 +++++++++---------------
include/linux/device.h | 12 +++++
8 files changed, 79 insertions(+), 67 deletions(-)
next reply other threads:[~2021-01-24 12:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-24 12:58 Greg KH [this message]
2021-01-24 19:33 ` [GIT PULL] Driver core fixes for 5.11-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=YA1u+IPixwAx6t7P@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;
as well as URLs for NNTP newsgroup(s).