linux-kernel - Re: [PATCH v2] gpio: omap: do not register driver in probe()

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <176958902316.4537.1901338597465599154.b4-ty@oss.qualcomm.com>
Date: Wed, 28 Jan 2026 09:34:37 +0100
From: Bartosz Golaszewski <bartosz.golaszewski@....qualcomm.com>
To: gregkh@...uxfoundation.org, rafael@...nel.org, broonie@...nel.org,
        will@...nel.org, grygorii.strashko@...com, ssantosh@...nel.org,
        khilman@...nel.org, linusw@...nel.org, brgl@...nel.org,
        Danilo Krummrich <dakr@...nel.org>
Cc: Bartosz Golaszewski <bartosz.golaszewski@....qualcomm.com>,
        driver-core@...ts.linux.dev, linux-kernel@...r.kernel.org,
        linux-omap@...r.kernel.org, linux-gpio@...r.kernel.org
Subject: Re: [PATCH v2] gpio: omap: do not register driver in probe()


On Tue, 27 Jan 2026 21:17:12 +0100, Danilo Krummrich wrote:
> Commit 11a78b794496 ("ARM: OMAP: MPUIO wake updates") registers the
> omap_mpuio_driver from omap_mpuio_init(), which is called from
> omap_gpio_probe().
> 
> However, it neither makes sense to register drivers from probe()
> callbacks of other drivers, nor does the driver core allow registering
> drivers with a device lock already being held.
> 
> [...]

Applied, thanks!

[1/1] gpio: omap: do not register driver in probe()
      https://git.kernel.org/brgl/c/730e5ebff40c852e3ea57b71bf02a4b89c69435f

Best regards,
-- 
Bartosz Golaszewski <bartosz.golaszewski@....qualcomm.com>