From: Greg KH <gregkh@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Danilo Krummrich <dakr@kernel.org>,
linux-kernel@vger.kernel.org,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: [GIT PULL] Driver core fixes for 6.15-rc4
Date: Fri, 25 Apr 2025 15:47:55 +0200 [thread overview]
Message-ID: <aAuSi9YCYEN46yXf@kroah.com> (raw)
The following changes since commit 0af2f6be1b4281385b618cb86ad946eded089ac8:
Linux 6.15-rc1 (2025-04-06 13:11:33 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/driver-core/driver-core.git tags/driver-core-6.15-rc4
for you to fetch changes up to b9792abb76ae1649080b8d48092c52e24c7bbdc2:
drivers/base/memory: Avoid overhead from for_each_present_section_nr() (2025-04-15 18:19:49 +0200)
----------------------------------------------------------------
Driver core fixes for 6.15-rc4
Here are some small driver core fixes to resolve a number of reported
problems. Included in here are:
- driver core sync fix revert to resolve a much reported problem,
hopefully this is finally resolved
- MAINTAINERS file update, documenting that the driver-core tree is
now under a "shared" maintainership model, thanks to Rafael and
Danilo for offering to do this!
- auxbus documentation and MAINTAINERS file update
- MAINTAINERS file update for Rust PCI code
- firmware rust binding fixup
- software node link fix
All of these have been in linux-next for over a week with no reported
issues.
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
----------------------------------------------------------------
Andy Shevchenko (1):
device property: Add a note to the fwnode.h
Christian Schrefl (1):
rust: firmware: Use `ffi::c_char` type in `FwFunc`
Danilo Krummrich (1):
MAINTAINERS: pci: add entry for Rust PCI code
Dmitry Torokhov (3):
Revert "drivers: core: synchronize really_probe() and dev_uevent()"
driver core: introduce device_set_driver() helper
driver core: fix potential NULL pointer dereference in dev_uevent()
Gavin Shan (1):
drivers/base/memory: Avoid overhead from for_each_present_section_nr()
Greg Kroah-Hartman (1):
MAINTAINERS: update the location of the driver-core git tree
Leon Romanovsky (2):
drivers/base: Extend documentation with preferred way to use auxbus
drivers/base: Add myself as auxiliary bus reviewer
Lizhi Xu (1):
software node: Prevent link creation failure from causing kobj reference count imbalance
MAINTAINERS | 17 ++++++++++++++---
drivers/base/auxiliary.c | 10 ++++++++++
drivers/base/base.h | 17 +++++++++++++++++
drivers/base/bus.c | 2 +-
drivers/base/core.c | 38 ++++++++++++++++++++++++++++++++------
drivers/base/dd.c | 7 +++----
drivers/base/memory.c | 41 +++++++++++++++++------------------------
drivers/base/swnode.c | 3 +--
include/linux/fwnode.h | 5 +++++
rust/kernel/firmware.rs | 8 ++++++--
10 files changed, 106 insertions(+), 42 deletions(-)
next reply other threads:[~2025-04-25 13:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-25 13:47 Greg KH [this message]
2025-04-25 18:01 ` 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=aAuSi9YCYEN46yXf@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=dakr@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@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
all inboxes | Powered by JetHome®