Linux driver-core infrastructure
 help / color / mirror / Atom feed
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@kernel.org>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	<driver-core@lists.linux.dev>, <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] Driver core fixes for 7.1-rc5
Date: Sat, 23 May 2026 15:10:04 +0200	[thread overview]
Message-ID: <DIQ2X70CYYKK.W7Q958FP7DBO@kernel.org> (raw)

Hi Linus,

Please pull these driver-core fixes.

Thanks,
Danilo

The following changes since commit 254f49634ee16a731174d2ae34bc50bd5f45e731:

  Linux 7.1-rc1 (2026-04-26 14:19:00 -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-7.1-rc5

for you to fetch changes up to 215c90ee656114f5e8c32408228d97082f8e0eef:

  device property: set fwnode->secondary to NULL in fwnode_init() (2026-05-22 12:24:08 +0200)

----------------------------------------------------------------
Driver core fixes for 7.1-rc5

- Remove the software node on platform device release(); without this,
  the software node remains registered after the device is gone and a
  subsequent platform_device_register_full() reusing the same node fails
  with -EBUSY

- In sysfs_update_group(), do not remove a pre-existing directory when
  create_files() fails; the previous code would silently destroy a sysfs
  group that the caller did not create

- Set fwnode->secondary to NULL in fwnode_init() to avoid dereferencing
  uninitialized memory (e.g. in dev_to_swnode()) when the firmware node
  is allocated on the stack or via a non-zeroing allocator

----------------------------------------------------------------
Bartosz Golaszewski (2):
      driver core: platform: remove software node on release()
      device property: set fwnode->secondary to NULL in fwnode_init()

Greg Kroah-Hartman (1):
      sysfs: don't remove existing directory on update failure

 drivers/base/platform.c | 16 +++++++++++++++-
 fs/sysfs/group.c        |  2 +-
 include/linux/fwnode.h  |  1 +
 3 files changed, 17 insertions(+), 2 deletions(-)

             reply	other threads:[~2026-05-23 13:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-23 13:10 Danilo Krummrich [this message]
2026-05-23 16:23 ` [GIT PULL] Driver core fixes for 7.1-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=DIQ2X70CYYKK.W7Q958FP7DBO@kernel.org \
    --to=dakr@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=driver-core@lists.linux.dev \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=saravanak@kernel.org \
    --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