[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <DFUA41G0WJ04.3TZX9914SM60E@kernel.org>
Date: Wed, 21 Jan 2026 13:50:52 +0100
From: "Danilo Krummrich" <dakr@...nel.org>
To: "Mark Brown" <broonie@...nel.org>
Cc: "Wang Jiayue" <akaieurus@...il.com>, <hanguidong02@...il.com>,
<gregkh@...uxfoundation.org>, <rafael@...nel.org>, <Aishwarya.TCV@....com>,
<chenqiuji666@...il.com>, <linux-kernel@...r.kernel.org>,
<m.szyprowski@...sung.com>, <robin.clark@....qualcomm.com>,
<will@...nel.org>, <robin.murphy@....com>, <joro@...tes.org>,
<iommu@...ts.linux.dev>
Subject: Re: [PATCH v5] driver core: enforce device_lock for
driver_match_device()
On Wed Jan 21, 2026 at 1:49 PM CET, Mark Brown wrote:
> On Wed, Jan 21, 2026 at 12:02:15PM +0100, Danilo Krummrich wrote:
>
>> I assume that this should resolve the problem (unless there are more drivers
>> that register drivers in probe()):
>
> This makes sense to me, I guess we can just fix any other instances as
> they arise. Will you send the patch?
Yes, I will send it soon.
Powered by blists - more mailing lists