From: "Danilo Krummrich" <dakr@kernel.org>
To: "Mark Brown" <broonie@kernel.org>
Cc: "Thomas Weißschuh" <linux@weissschuh.net>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
driver-core@lists.linux.dev, linux-kernel@vger.kernel.org,
"Zhang Yuwei" <zhangyuwei20@huawei.com>
Subject: Re: [PATCH v3 4/5] driver core: Allow the constification of device attributes
Date: Tue, 26 May 2026 17:32:22 +0200 [thread overview]
Message-ID: <DISPTSBBTHC8.2TJ91B1731ZS7@kernel.org> (raw)
In-Reply-To: <874d9889-1a2c-49b9-8d7c-f963fc21dae4@sirena.org.uk>
On Tue May 26, 2026 at 5:25 PM CEST, Mark Brown wrote:
> I've now got another bisect which comes out to another driver core
> commit 1137838865bf (driver core: Use mod_delayed_work to prevent lost
> deferred probe work), I don't know that that is an accurate result
> either but it does look like there's something fishy in this area.
When I saw your first mail I did already suspect that it might be this one, as
it is a race that might or might not trigger.
I applied [1] to driver-core-next today, so it should hopefully be fixed for
tomorrow's linux-next release.
[1] https://lore.kernel.org/driver-core/20260526145824.501263-1-dakr@kernel.org/T/#u
next prev parent reply other threads:[~2026-05-26 15:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 16:39 [PATCH v3 0/5] driver core: Allow the constification of device attributes Thomas Weißschuh
2026-05-12 16:39 ` [PATCH v3 1/5] driver core: Delete DEVICE_ATTR_PREALLOC() Thomas Weißschuh
2026-05-12 16:39 ` [PATCH v3 2/5] driver core: Add low-level macros for device attributes Thomas Weißschuh
2026-05-12 16:39 ` [PATCH v3 3/5] driver core: Stop using generic sysfs " Thomas Weißschuh
2026-05-12 16:39 ` [PATCH v3 4/5] driver core: Allow the constification of " Thomas Weißschuh
2026-05-26 14:52 ` Mark Brown
2026-05-26 15:25 ` Mark Brown
2026-05-26 15:32 ` Danilo Krummrich [this message]
2026-05-26 15:38 ` Mark Brown
2026-05-12 16:39 ` [PATCH v3 5/5] driver core: Constify core " Thomas Weißschuh
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=DISPTSBBTHC8.2TJ91B1731ZS7@kernel.org \
--to=dakr@kernel.org \
--cc=broonie@kernel.org \
--cc=driver-core@lists.linux.dev \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=rafael@kernel.org \
--cc=zhangyuwei20@huawei.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.