public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: Philipp Zabel <p.zabel@pengutronix.de>
Cc: 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, imx@lists.linux.dev,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org,
	Frank Li <Frank.Li@nxp.com>
Subject: Re: [PATCH v2] drm/imx/tve: fix probe device leak
Date: Wed, 14 Jan 2026 11:58:14 +0100	[thread overview]
Message-ID: <aWd2xizOQAnVRaSs@hovoldconsulting.com> (raw)
In-Reply-To: <aR8TWJurF1a0LLGJ@hovoldconsulting.com>

On Thu, Nov 20, 2025 at 02:10:48PM +0100, Johan Hovold wrote:
> On Thu, Oct 30, 2025 at 05:34:56PM +0100, Johan Hovold wrote:
> > Make sure to drop the reference taken to the DDC device during probe on
> > probe failure (e.g. probe deferral) and on driver unbind.
> > 
> > Fixes: fcbc51e54d2a ("staging: drm/imx: Add support for Television Encoder (TVEv2)")
> > Cc: stable@vger.kernel.org	# 3.10
> > Cc: Philipp Zabel <p.zabel@pengutronix.de>
> > Reviewed-by: Frank Li <Frank.Li@nxp.com>
> > Signed-off-by: Johan Hovold <johan@kernel.org>
> > ---
> > 
> > Changes in v2:
> >  - add missing NULL ddc check
> 
> Can this one be picked up for 6.19?

It's been two more months so sending another reminder.

Can this one be merged now?

Johan

  reply	other threads:[~2026-01-14 10:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-30 16:34 [PATCH v2] drm/imx/tve: fix probe device leak Johan Hovold
2025-11-20 13:10 ` Johan Hovold
2026-01-14 10:58   ` Johan Hovold [this message]
2026-01-27 15:59     ` Johan Hovold
2026-01-28  9:58       ` Maxime Ripard
2026-01-28 10:03         ` Johan Hovold

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=aWd2xizOQAnVRaSs@hovoldconsulting.com \
    --to=johan@kernel.org \
    --cc=Frank.Li@nxp.com \
    --cc=airlied@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=imx@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=p.zabel@pengutronix.de \
    --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