From: "Danilo Krummrich" <dakr@kernel.org>
To: "Ulf Hansson" <ulf.hansson@linaro.org>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
<gregkh@linuxfoundation.org>, <saravanak@kernel.org>,
<driver-core@lists.linux.dev>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] driver core: use READ_ONCE() for dev->driver in dev_has_sync_state()
Date: Mon, 04 May 2026 20:59:45 +0200 [thread overview]
Message-ID: <DIA4GKZMIFBT.27APOZ08MTDPX@kernel.org> (raw)
In-Reply-To: <CAPDyKFo6Jyq+VTVvrX=DkQoxbGVi4cunvsNYya6oyz7=OZY6BA@mail.gmail.com>
On Mon May 4, 2026 at 8:43 PM CEST, Ulf Hansson wrote:
> On Mon, 4 May 2026 at 12:30, Danilo Krummrich <dakr@kernel.org> wrote:
>>
>> On Mon May 4, 2026 at 11:49 AM CEST, Ulf Hansson wrote:
>> > Apologize for the delay. Genpd needs the function [1] when it tries to
>> > assign a common ->sync_state() callback for its providers.
>>
>> Can you add a revert of [1] to your patch series, so it gets (re-)exported with
>> a user?
>
> Yes!
>
> I was trying to avoid dependent changes to the driver core to funnel
> my series entirely through my pmdomain tree. Anyway, perhaps you can
> host an immutable branch for me to pull in, in this case.
I think you can just make the revert the first patch in your series and when it
is ready I can pick up only the revert in the driver-core tree; everything else
can go through your pmdomain tree.
I.e. you don't need the revert in your pmdomain tree as it should still have
dev_has_sync_state() exported in device.h.
next prev parent reply other threads:[~2026-05-04 18:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-18 16:22 [PATCH] driver core: use READ_ONCE() for dev->driver in dev_has_sync_state() Danilo Krummrich
2026-04-18 19:16 ` Saravana Kannan
2026-04-19 14:40 ` Greg KH
2026-04-20 10:40 ` Rafael J. Wysocki
2026-05-04 9:49 ` Ulf Hansson
2026-05-04 10:30 ` Danilo Krummrich
2026-05-04 18:43 ` Ulf Hansson
2026-05-04 18:59 ` Danilo Krummrich [this message]
2026-04-28 22:38 ` 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=DIA4GKZMIFBT.27APOZ08MTDPX@kernel.org \
--to=dakr@kernel.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=ulf.hansson@linaro.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