From: Liu Ying <victor.liu@nxp.com>
To: Luca Ceresoli <luca.ceresoli@bootlin.com>,
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>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>
Cc: dri-devel@lists.freedesktop.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: (subset) [PATCH 0/3] drm/bridge: imx: A few fixes
Date: Wed, 28 Jan 2026 09:50:38 +0800 [thread overview]
Message-ID: <f11d4407-9951-40a3-bde5-583ca1ca5bc5@nxp.com> (raw)
In-Reply-To: <176951374753.94588.10653964166300906894.b4-ty@bootlin.com>
Hi Luca,
On Tue, Jan 27, 2026 at 12:35:47PM +0100, Luca Ceresoli wrote:
>
> On Fri, 23 Jan 2026 17:22:14 +0800, Liu Ying wrote:
>> This patch series contains 3 bug fixes for i.MX8QXP DRM bridges.
>> Each patch fixes a NULL pointer dereference issue and stands alone.
>>
>>
>
> Applied, thanks!
>
> [1/3] drm/bridge: imx8qxp-ldb: Fix NULL pointer dereference in imx8qxp_ldb_bridge_destroy()
> commit: 852c68bf42965ee38b465d2d6f7b965eb0b5dc1d
> [2/3] drm/bridge: imx8qxp-pxl2dpi: Fix NULL pointer dereference in imx8qxp_pxl2dpi_bridge_destroy()
> commit: db7e7ea838c916ee4cdf26bee126fd36f58295dc
Any reason why patch 3/3 is not applied?
>
> Best regards,
--
Regards,
Liu Ying
next prev parent reply other threads:[~2026-01-28 1:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-23 9:22 [PATCH 0/3] drm/bridge: imx: A few fixes Liu Ying
2026-01-23 9:22 ` [PATCH 1/3] drm/bridge: imx8qxp-ldb: Fix NULL pointer dereference in imx8qxp_ldb_bridge_destroy() Liu Ying
2026-01-23 14:55 ` Frank Li
2026-01-26 8:29 ` Luca Ceresoli
2026-01-23 9:22 ` [PATCH 2/3] drm/bridge: imx8qxp-pxl2dpi: Fix NULL pointer dereference in imx8qxp_pxl2dpi_bridge_destroy() Liu Ying
2026-01-23 14:56 ` Frank Li
2026-01-26 8:30 ` Luca Ceresoli
2026-01-23 9:22 ` [PATCH 3/3] drm/bridge: imx8qxp-pixel-combiner: Fix bailout for imx8qxp_pc_bridge_probe() Liu Ying
2026-01-23 14:57 ` Frank Li
2026-01-26 8:33 ` Luca Ceresoli
2026-01-26 8:47 ` Liu Ying
2026-01-26 8:51 ` Luca Ceresoli
2026-01-27 11:35 ` (subset) [PATCH 0/3] drm/bridge: imx: A few fixes Luca Ceresoli
2026-01-28 1:50 ` Liu Ying [this message]
2026-01-28 15:26 ` Luca Ceresoli
2026-01-28 17:59 ` Luca Ceresoli
2026-01-29 3:41 ` Liu Ying
2026-02-03 16:53 ` 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=f11d4407-9951-40a3-bde5-583ca1ca5bc5@nxp.com \
--to=victor.liu@nxp.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=airlied@gmail.com \
--cc=andrzej.hajda@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.ceresoli@bootlin.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=rfoss@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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