From: "Danilo Krummrich" <dakr@kernel.org>
To: "Linus Torvalds" <torvalds@linux-foundation.org>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
"Saravana Kannan" <saravanak@google.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
<rust-for-linux@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] Driver core fixes for 6.18-rc3
Date: Sat, 25 Oct 2025 13:57:06 +0200 [thread overview]
Message-ID: <DDRDUX7T9JLZ.NO8N2TZOIWFO@kernel.org> (raw)
Hi Linus,
Please pull these driver-core fixes.
All commits have been in linux-next for a couple rounds; no conflicts expected.
- Danilo
The following changes since commit 3a8660878839faadb4f1a6dd72c3179c1df56787:
Linux 6.18-rc1 (2025-10-12 13:42:36 -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.18-rc3
for you to fetch changes up to 2eead19334516c8e9927c11b448fbe512b1f18a1:
arch_topology: Fix incorrect error check in topology_parse_cpu_capacity() (2025-10-22 08:06:28 +0200)
----------------------------------------------------------------
Driver core fixes for 6.18-rc3
- In Device::parent(), do not make any assumptions on the device
context of the parent device.
- Check visibility before changing ownership of a sysfs attribute
group.
- In topology_parse_cpu_capacity(), replace an incorrect usage of
PTR_ERR_OR_ZERO() with IS_ERR_OR_NULL().
- In devcoredump, fix a circular locking dependency between
struct devcd_entry::mutex and kernfs.
- Do not warn about a pending fw_devlink sync state.
----------------------------------------------------------------
Danilo Krummrich (1):
rust: device: fix device context of Device::parent()
Fernando Fernandez Mancera (1):
sysfs: check visibility before changing group attribute ownership
Kaushlendra Kumar (1):
arch_topology: Fix incorrect error check in topology_parse_cpu_capacity()
Maarten Lankhorst (1):
devcoredump: Fix circular locking dependency with devcd->mutex.
Ulf Hansson (1):
driver core: fw_devlink: Don't warn about sync_state() pending
drivers/base/arch_topology.c | 2 +-
drivers/base/core.c | 2 +-
drivers/base/devcoredump.c | 136 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++------------------------------------------------
fs/sysfs/group.c | 26 +++++++++++++++++++-----
rust/kernel/auxiliary.rs | 8 +-------
rust/kernel/device.rs | 4 ++--
6 files changed, 109 insertions(+), 69 deletions(-)
next reply other threads:[~2025-10-25 11:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-25 11:57 Danilo Krummrich [this message]
2025-10-25 18:12 ` 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=DDRDUX7T9JLZ.NO8N2TZOIWFO@kernel.org \
--to=dakr@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=saravanak@google.com \
--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®