All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Danilo Krummrich" <dakr@kernel.org>
To: "Bartosz Golaszewski" <brgl@kernel.org>
Cc: <gregkh@linuxfoundation.org>, <rafael@kernel.org>,
	<broonie@kernel.org>, <will@kernel.org>,
	<grygorii.strashko@ti.com>, <ssantosh@kernel.org>,
	<khilman@kernel.org>, <linusw@kernel.org>,
	<driver-core@lists.linux.dev>, <linux-kernel@vger.kernel.org>,
	<linux-omap@vger.kernel.org>, <linux-gpio@vger.kernel.org>
Subject: Re: [PATCH] gpio: omap: do not register driver in probe()
Date: Mon, 26 Jan 2026 12:35:51 +0100	[thread overview]
Message-ID: <DFYHNBNEFFNC.3V8T0ZGKEDYSJ@kernel.org> (raw)
In-Reply-To: <CAMRc=MctBqEcoDOG6BGtd=ri-c9X9awnfrojtYRVPQfp8EfGdQ@mail.gmail.com>

On Mon Jan 26, 2026 at 10:06 AM CET, Bartosz Golaszewski wrote:
> On Fri, Jan 23, 2026 at 2:44 PM Danilo Krummrich <dakr@kernel.org> wrote:
>>
>> On Fri Jan 23, 2026 at 2:31 PM CET, Danilo Krummrich wrote:
>> > However, for the purpose of avoiding the described potential deadlock in
>> > combination with commit dc23806a7c47 ("driver core: enforce device_lock for
>> > driver_match_device()"), this patch only addresses the driver registration
>> > issue.
>>
>> I.e. unless there are any concerns, I'd like to take this one through the
>> driver-core tree.
>
> It looks good to me, but it's a GPIO driver, this can go together with
> GPIO fixes for v6.19-rc8 as usual.

Commit [1] reveals the issue and was originally scheduled for a driver-core
fixes PR, so it made sense for this patch to go together with [1]. However, I
told Linus [2] that I will hold back [1] for now and send it with the -rc1 PR to
give it some more time in linux-next.

So, if you can take this patch for -rc8, that'd be great.

Thanks,
Danilo

[1] dc23806a7c47 ("driver core: enforce device_lock for driver_match_device()")
[2] https://lore.kernel.org/driver-core/DFWVL46MM928.V9LOBRWI8BLZ@kernel.org/

  reply	other threads:[~2026-01-26 11:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-23 13:31 [PATCH] gpio: omap: do not register driver in probe() Danilo Krummrich
2026-01-23 13:44 ` Danilo Krummrich
2026-01-26  9:06   ` Bartosz Golaszewski
2026-01-26 11:35     ` Danilo Krummrich [this message]
2026-01-23 13:57 ` Danilo Krummrich
2026-01-23 14:19   ` Greg KH
2026-01-23 14:25     ` Danilo Krummrich
2026-01-23 15:23       ` Greg KH
2026-01-23 15:48         ` Danilo Krummrich
2026-01-27  9:09 ` Bartosz Golaszewski
2026-01-27 13:37   ` Danilo Krummrich
2026-01-27 19:26     ` Bartosz Golaszewski

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=DFYHNBNEFFNC.3V8T0ZGKEDYSJ@kernel.org \
    --to=dakr@kernel.org \
    --cc=brgl@kernel.org \
    --cc=broonie@kernel.org \
    --cc=driver-core@lists.linux.dev \
    --cc=gregkh@linuxfoundation.org \
    --cc=grygorii.strashko@ti.com \
    --cc=khilman@kernel.org \
    --cc=linusw@kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=ssantosh@kernel.org \
    --cc=will@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 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.