[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <176399066927.969838.15946277530835988104.b4-ty@foss.st.com>
Date: Mon, 24 Nov 2025 14:27:04 +0100
From: Raphael Gallais-Pou <raphael.gallais-pou@...s.st.com>
To: Alain Volmat <alain.volmat@...s.st.com>,
Raphael Gallais-Pou
<rgallaispou@...il.com>,
Johan Hovold <johan@...nel.org>
CC: Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
Maxime Ripard
<mripard@...nel.org>,
Thomas Zimmermann <tzimmermann@...e.de>,
David Airlie
<airlied@...il.com>, Simona Vetter <simona@...ll.ch>,
<dri-devel@...ts.freedesktop.org>, <linux-kernel@...r.kernel.org>,
<stable@...r.kernel.org>,
Benjamin Gaignard <benjamin.gaignard@...labora.com>
Subject: Re: [PATCH] drm: sti: fix device leaks at component probe
On Mon, 22 Sep 2025 14:20:12 +0200, Johan Hovold wrote:
> Make sure to drop the references taken to the vtg devices by
> of_find_device_by_node() when looking up their driver data during
> component probe.
>
> Note that holding a reference to a platform device does not prevent its
> driver data from going away so there is no point in keeping the
> reference after the lookup helper returns.
>
> [...]
Hi Johan,
Applied, thanks!
[1/1] drm: sti: fix device leaks at component probe
commit: 620a8f131154250f6a64a07d049a4f235d6451a5
Best regards,
--
Raphael Gallais-Pou <raphael.gallais-pou@...s.st.com>
Powered by blists - more mailing lists