From: Luca Ceresoli <luca.ceresoli@bootlin.com>
To: Andy Yan <andy.yan@rock-chips.com>,
Osama Abdelkader <osama.abdelkader@gmail.com>
Cc: stable@vger.kernel.org, Andrzej Hajda <andrzej.hajda@intel.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
Robert Foss <rfoss@kernel.org>,
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>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] drm/bridge: synopsys: dw-dp: fix error paths of dw_dp_bind
Date: Tue, 20 Jan 2026 15:32:38 +0100 [thread overview]
Message-ID: <176891955882.652956.206927403017627596.b4-ty@bootlin.com> (raw)
In-Reply-To: <20260102155553.13243-1-osama.abdelkader@gmail.com>
On Fri, 02 Jan 2026 16:55:52 +0100, Osama Abdelkader wrote:
> Fix several issues in dw_dp_bind() error handling:
>
> 1. Missing return after drm_bridge_attach() failure - the function
> continued execution instead of returning an error.
>
> 2. Resource leak: drm_dp_aux_register() is not a devm function, so
> drm_dp_aux_unregister() must be called on all error paths after
> aux registration succeeds. This affects errors from:
> - drm_bridge_attach()
> - phy_init()
> - devm_add_action_or_reset()
> - platform_get_irq()
> - devm_request_threaded_irq()
>
> [...]
Applied, thanks!
[1/1] drm/bridge: synopsys: dw-dp: fix error paths of dw_dp_bind
commit: 1a0f69e3c28477b97d3609569b7e8feb4b6162e8
Best regards,
--
Luca Ceresoli <luca.ceresoli@bootlin.com>
prev parent reply other threads:[~2026-01-20 14:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-02 15:55 Osama Abdelkader
2026-01-05 11:20 ` Luca Ceresoli
2026-01-20 9:34 ` Louis Chauvet
2026-01-20 14:32 ` Luca Ceresoli [this message]
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=176891955882.652956.206927403017627596.b4-ty@bootlin.com \
--to=luca.ceresoli@bootlin.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=airlied@gmail.com \
--cc=andrzej.hajda@intel.com \
--cc=andy.yan@rock-chips.com \
--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=osama.abdelkader@gmail.com \
--cc=rfoss@kernel.org \
--cc=simona@ffwll.ch \
--cc=stable@vger.kernel.org \
--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
all inboxes | Powered by JetHome®