From: "Raphaël Gallais-Pou" <rgallaispou@gmail.com>
To: Osama Abdelkader <osama.abdelkader@gmail.com>,
luca.ceresoli@bootlin.com,
Alain Volmat <alain.volmat@foss.st.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>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Cc: stable@vger.kernel.org
Subject: Re: [PATCH v3 1/3] drm/sti: remove bridge when sti_hda component_add fails
Date: Wed, 29 Apr 2026 15:40:28 +0200 [thread overview]
Message-ID: <2d81e7f6-b6e4-4e3e-bd75-315c696c003a@gmail.com> (raw)
In-Reply-To: <20260423200622.325076-1-osama.abdelkader@gmail.com>
On 4/23/26 22:06, Osama Abdelkader wrote:
> Use devm_drm_bridge_add() so the bridge is released if probe fails after
> registration, and drop the manual drm_bridge_remove() in remove().
>
> Check the return value of devm_drm_bridge_add().
>
> Signed-off-by: Osama Abdelkader <osama.abdelkader@gmail.com>
> Fixes: d28726efc637 ("drm/sti: hda: add bridge before attaching")
> Cc: stable@vger.kernel.org
> ---
Hi Osama,
Acked-by: Raphaël Gallais-Pou <rgallaispou@gmail.com>
Thanks,
Best regards,
Raphaël
next prev parent reply other threads:[~2026-04-29 13:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-23 20:06 [PATCH v3 1/3] drm/sti: remove bridge when sti_hda component_add fails Osama Abdelkader
2026-04-23 20:06 ` [PATCH v3 2/3] drm/exynos: remove bridge when " Osama Abdelkader
2026-04-29 11:43 ` Luca Ceresoli
2026-05-04 20:47 ` Raphaël Gallais-Pou
2026-04-23 20:06 ` [PATCH v3 3/3] drm/bridge: megachips: remove bridge when irq request fails Osama Abdelkader
2026-04-29 11:48 ` Luca Ceresoli
2026-04-30 20:00 ` Osama Abdelkader
2026-04-29 11:42 ` [PATCH v3 1/3] drm/sti: remove bridge when sti_hda component_add fails Luca Ceresoli
2026-04-29 13:40 ` Raphaël Gallais-Pou [this message]
2026-05-04 20:58 ` Raphael Gallais-Pou
2026-05-05 14:57 ` (subset) " Luca Ceresoli
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=2d81e7f6-b6e4-4e3e-bd75-315c696c003a@gmail.com \
--to=rgallaispou@gmail.com \
--cc=airlied@gmail.com \
--cc=alain.volmat@foss.st.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.ceresoli@bootlin.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=osama.abdelkader@gmail.com \
--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