From: "Danilo Krummrich" <dakr@kernel.org>
To: "Johan Hovold" <johan@kernel.org>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Rafael J . Wysocki" <rafael@kernel.org>,
<driver-core@lists.linux.dev>, <linux-kernel@vger.kernel.org>,
<stable@vger.kernel.org>
Subject: Re: [PATCH] driver core: reject devices with unregistered buses
Date: Wed, 29 Apr 2026 17:29:02 +0200 [thread overview]
Message-ID: <DI5QUINEJC6U.32I161SD0KU76@kernel.org> (raw)
In-Reply-To: <afIe495IbAe7EeDt@hovoldconsulting.com>
On Wed Apr 29, 2026 at 5:08 PM CEST, Johan Hovold wrote:
> No, I'm saying that it's a bug in driver core to silently treat a device
> that is registered before its bus as a bus-less device.
This is an argument that I can buy into, but in the previous discussion (and in
the commit message) the whole motivation evolved around "reject devices with
unregistered buses to catch any callers that get the ordering wrong", i.e. catch
other people's bugs.
What you are raising now is "the driver core is conflating no bus with
unregistered bus handling". However, the commit message does not reflect that at
all.
Can you please adjust the commit message accordingly?
(As for the stable question, I don't think this changes anything though.)
next prev parent reply other threads:[~2026-04-29 15:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-27 10:28 [PATCH] driver core: reject devices with unregistered buses Johan Hovold
2026-04-28 19:09 ` Danilo Krummrich
2026-04-29 10:11 ` Johan Hovold
2026-04-29 11:11 ` Danilo Krummrich
2026-04-29 11:33 ` Johan Hovold
2026-04-29 14:52 ` Danilo Krummrich
2026-04-29 15:08 ` Johan Hovold
2026-04-29 15:29 ` Danilo Krummrich [this message]
2026-04-29 16:00 ` Johan Hovold
2026-04-29 16:18 ` Danilo Krummrich
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=DI5QUINEJC6U.32I161SD0KU76@kernel.org \
--to=dakr@kernel.org \
--cc=driver-core@lists.linux.dev \
--cc=gregkh@linuxfoundation.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=stable@vger.kernel.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