From: Johan Hovold <johan@kernel.org>
To: Andrzej Hajda <andrzej.hajda@intel.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
Robert Foss <rfoss@kernel.org>
Cc: Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
Jonas Karlman <jonas@kwiboo.se>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Douglas Anderson <dianders@chromium.org>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Johan Hovold <johan@kernel.org>
Subject: [PATCH 0/2] drm/bridge: fix OF node leaks
Date: Tue, 8 Jul 2025 10:51:22 +0200 [thread overview]
Message-ID: <20250708085124.15445-1-johan@kernel.org> (raw)
Make sure to drop the OF node references taken when creating bridge
device when the devices are later released.
Johan
Johan Hovold (2):
drm/bridge: fix OF node leak
drm/bridge: ti-sn65dsi86: fix OF node leak
drivers/gpu/drm/bridge/aux-bridge.c | 2 ++
drivers/gpu/drm/bridge/ti-sn65dsi86.c | 2 ++
2 files changed, 4 insertions(+)
--
2.49.0
next reply other threads:[~2025-07-08 8:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-08 8:51 Johan Hovold [this message]
2025-07-08 8:51 ` [PATCH 1/2] drm/bridge: fix OF node leak Johan Hovold
2025-07-24 10:03 ` Johan Hovold
2025-08-02 17:45 ` Dmitry Baryshkov
2025-07-08 8:51 ` [PATCH 2/2] drm/bridge: ti-sn65dsi86: " Johan Hovold
2025-07-14 18:46 ` Doug Anderson
2025-07-15 7:09 ` Johan Hovold
2025-08-02 18:27 ` (subset) [PATCH 0/2] drm/bridge: fix OF node leaks Dmitry Baryshkov
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=20250708085124.15445-1-johan@kernel.org \
--to=johan@kernel.org \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=airlied@gmail.com \
--cc=andrzej.hajda@intel.com \
--cc=dianders@chromium.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=rfoss@kernel.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).