From: "Danilo Krummrich" <dakr@kernel.org>
To: "Cristian Marussi" <cristian.marussi@arm.com>
Cc: "Gui-Dong Han" <hanguidong02@gmail.com>,
<gregkh@linuxfoundation.org>, <rafael@kernel.org>,
<linux-kernel@vger.kernel.org>, <baijiaju1990@gmail.com>,
"Qiu-ji Chen" <chenqiuji666@gmail.com>,
<gatien.chevallier@foss.st.com>, <sudeep.holla@kernel.org>,
<arm-scmi@vger.kernel.org>
Subject: Re: [PATCH v5] driver core: enforce device_lock for driver_match_device()
Date: Wed, 25 Feb 2026 21:38:01 +0100 [thread overview]
Message-ID: <DGOBYS4LNHWW.2JTHJHGQA37C@kernel.org> (raw)
In-Reply-To: <aZ9ZN7H1thCmkPEQ@pluto>
On Wed Feb 25, 2026 at 9:19 PM CET, Cristian Marussi wrote:
> it has been reported by Gatien (in CC) that this break the SCMI OPTEE
> transport.
>
> Moreover I still have to verify, BUT I think this also breaks SCMI
> Virtio transport since both call platform_driver_register() during their
> probe, since a few years ago the SCMI transports have been reworked to be
> standalone full-fledged drivers.
I've had a quick look and I'm pretty sure that both transports/virtio.c and
transports/optee.c are broken.
Both cases look identical and I think the fix should be as trivial as moving
platform_driver_register() into module_init().
> I'll have a look in the next days if we can cope with this.
I already fixed those three [1,2,3]. If you can provide a patch for both of
them, that'd be great. Otherwise, please let me know if you want me to send
something.
Thanks,
Danilo
[1] https://lore.kernel.org/driver-core/20260121141215.29658-1-dakr@kernel.org/
[2] https://lore.kernel.org/driver-core/20260123133614.72586-1-dakr@kernel.org/
[3] https://lore.kernel.org/driver-core/20260212235842.85934-1-dakr@kernel.org/
next prev parent reply other threads:[~2026-02-25 20:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260113162843.12712-1-hanguidong02@gmail.com>
2026-02-25 20:19 ` [PATCH v5] driver core: enforce device_lock for driver_match_device() Cristian Marussi
2026-02-25 20:38 ` Danilo Krummrich [this message]
2026-02-26 8:54 ` Gatien CHEVALLIER
2026-02-26 11:15 ` Danilo Krummrich
2026-02-26 12:21 ` Cristian Marussi
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=DGOBYS4LNHWW.2JTHJHGQA37C@kernel.org \
--to=dakr@kernel.org \
--cc=arm-scmi@vger.kernel.org \
--cc=baijiaju1990@gmail.com \
--cc=chenqiuji666@gmail.com \
--cc=cristian.marussi@arm.com \
--cc=gatien.chevallier@foss.st.com \
--cc=gregkh@linuxfoundation.org \
--cc=hanguidong02@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=sudeep.holla@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