public inbox for linux-kernel@vger.kernel.org
 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-rc1
Date: Sun, 19 Apr 2026 17:43:18 +0200	[thread overview]
Message-ID: <DHX8VZYC4ZPZ.10EVXYC94K10Q@kernel.org> (raw)

Hi Linus,

Please pull these driver-core fixes.

All commits have been in linux-next for 5 rounds (4 for the kernel-doc fix); no
conflicts expected.

I also included a software node patch from Bartosz; it's not strictly a fix, but
he has follow-up patches building on it across various trees, so including it
for -rc1 still seemed like the pragmatic choice. I hope this is fine with you.

- Danilo

The following changes since commit c369299895a591d96745d6492d4888259b004a9e:

  Linux 7.0-rc5 (2026-03-22 14:42:17 -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-rc1-2

for you to fetch changes up to 5b484311507b5d403c1f7a45f6aa3778549e268b:

  driver core: Add kernel-doc for DEV_FLAG_COUNT enum value (2026-04-14 11:27:27 +0200)

----------------------------------------------------------------
Driver core fixes for 7.1-rc1

- Prevent a device from being probed before device_add() has finished
  initializing it; gate probe with a "ready_to_probe" device flag to
  avoid races with concurrent driver_register() calls

- Fix a kernel-doc warning for DEV_FLAG_COUNT introduced by the above

- Return -ENOTCONN from software_node_get_reference_args() when a
  referenced software node is known but not yet registered, allowing
  callers to defer probe

- In sysfs_group_attrs_change_owner(), also check is_visible_const();
  missed when the const variant was introduced

----------------------------------------------------------------
Bartosz Golaszewski (1):
      software node: return -ENOTCONN when referenced swnode is not registered yet

Douglas Anderson (2):
      driver core: Don't let a device probe until it's ready
      driver core: Add kernel-doc for DEV_FLAG_COUNT enum value

Thomas Weißschuh (1):
      sysfs: attribute_group: Respect is_visible_const() when changing owner

 drivers/base/core.c     | 15 +++++++++++++++
 drivers/base/dd.c       | 20 ++++++++++++++++++++
 drivers/base/property.c |  2 ++
 drivers/base/swnode.c   |  2 +-
 fs/sysfs/group.c        |  7 +++++--
 include/linux/device.h  | 45 +++++++++++++++++++++++++++++++++++++++++++++
 6 files changed, 88 insertions(+), 3 deletions(-)

             reply	other threads:[~2026-04-19 15:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-19 15:43 Danilo Krummrich [this message]
2026-04-19 20:28 ` [GIT PULL] Driver core fixes for 7.1-rc1 Linus Torvalds
2026-04-20  0:04   ` Danilo Krummrich
2026-04-19 21:53 ` 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=DHX8VZYC4ZPZ.10EVXYC94K10Q@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