AMD-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Hung <alex.hung@amd.com>
To: Chaitanya Kumar Borah <chaitanya.kumar.borah@intel.com>,
	dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
	intel-xe@lists.freedesktop.org, amd-gfx@lists.freedesktop.org
Cc: harry.wentland@amd.com, jani.nikula@linux.intel.com,
	louis.chauvet@bootlin.com, mwen@igalia.com, contact@emersion.fr,
	daniels@collabora.com, uma.shankar@intel.com,
	suraj.kandpal@intel.com, nfraprado@collabora.com,
	ville.syrjala@linux.intel.com, matthew.d.roper@intel.com
Subject: Re: [PATCH 12/13] drm/colorop: Use destroy callback for color pipeline teardown
Date: Tue, 6 Jan 2026 17:05:31 -0700	[thread overview]
Message-ID: <924e88fe-e2ff-4faf-8800-a056ef775599@amd.com> (raw)
In-Reply-To: <20251219065614.190834-13-chaitanya.kumar.borah@intel.com>

Reviewed-by: Alex Hung <alex.hung@amd.com>

On 12/18/25 23:56, Chaitanya Kumar Borah wrote:
> Switch drm_colorop_pipeline_destroy() to use the driver-provided
> destroy callback instead of directly calling drm_colorop_cleanup()
> and freeing the object.
> 
> This allows drivers that embed struct drm_colorop in driver-specific
> objects to perform correct teardown.
> 
> Signed-off-by: Chaitanya Kumar Borah <chaitanya.kumar.borah@intel.com>
> ---
>   drivers/gpu/drm/drm_colorop.c | 3 +--
>   1 file changed, 1 insertion(+), 2 deletions(-)
> 
> diff --git a/drivers/gpu/drm/drm_colorop.c b/drivers/gpu/drm/drm_colorop.c
> index 4b27804bb0bd..fafe45b93ff8 100644
> --- a/drivers/gpu/drm/drm_colorop.c
> +++ b/drivers/gpu/drm/drm_colorop.c
> @@ -205,8 +205,7 @@ void drm_colorop_pipeline_destroy(struct drm_device *dev)
>   	struct drm_colorop *colorop, *next;
>   
>   	list_for_each_entry_safe(colorop, next, &config->colorop_list, head) {
> -		drm_colorop_cleanup(colorop);
> -		kfree(colorop);
> +		colorop->funcs->destroy(colorop);
>   	}
>   }
>   EXPORT_SYMBOL(drm_colorop_pipeline_destroy);


  parent reply	other threads:[~2026-01-07  0:05 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-19  6:56 [PATCH 00/13] drm: Color pipeline teardown and follow-up fixes/improvements Chaitanya Kumar Borah
2025-12-19  6:56 ` [PATCH 01/13] drm/i915/color: Place 3D LUT after CSC in plane color pipeline Chaitanya Kumar Borah
2026-01-05  8:33   ` Kandpal, Suraj
2026-01-06  9:48   ` Shankar, Uma
2025-12-19  6:56 ` [PATCH 02/13] drm/amd/display: Fix color pipeline enum name leak Chaitanya Kumar Borah
2026-01-06 10:55   ` Shankar, Uma
2026-01-06 23:50   ` Alex Hung
2025-12-19  6:56 ` [PATCH 03/13] drm/vkms: " Chaitanya Kumar Borah
2026-01-06 10:57   ` Shankar, Uma
2026-01-06 23:50   ` Alex Hung
2025-12-19  6:56 ` [PATCH 04/13] drm/i915/display: " Chaitanya Kumar Borah
2026-01-05  9:04   ` Kandpal, Suraj
2026-01-06 10:59   ` Shankar, Uma
2025-12-19  6:56 ` [PATCH 05/13] drm: Allow driver-managed destruction of colorop objects Chaitanya Kumar Borah
2026-01-05  9:14   ` Kandpal, Suraj
2026-01-06 11:05   ` Shankar, Uma
2026-01-07  0:02   ` Alex Hung
2026-01-08 14:11     ` Borah, Chaitanya Kumar
2026-01-08 17:15       ` Alex Hung
2025-12-19  6:56 ` [PATCH 06/13] drm/colorop: Add destroy helper for " Chaitanya Kumar Borah
2026-01-05  9:16   ` Kandpal, Suraj
2026-01-06 11:07   ` Shankar, Uma
2026-01-07  0:02   ` Alex Hung
2025-12-19  6:56 ` [PATCH 07/13] drm/amd/display: Hook up colorop destroy helper for plane pipelines Chaitanya Kumar Borah
2026-01-06 11:10   ` Shankar, Uma
2026-01-07  0:03   ` Alex Hung
2025-12-19  6:56 ` [PATCH 08/13] drm/vkms: " Chaitanya Kumar Borah
2026-01-06 11:11   ` Shankar, Uma
2026-01-07  0:04   ` Alex Hung
2025-12-19  6:56 ` [PATCH 09/13] drm/i915/display: Hook up intel_colorop_destroy Chaitanya Kumar Borah
2026-01-05  9:18   ` Kandpal, Suraj
2026-01-06 11:16   ` Shankar, Uma
2025-12-19  6:56 ` [PATCH 10/13] drm: Clean up colorop objects during mode_config cleanup Chaitanya Kumar Borah
2026-01-05  9:20   ` Kandpal, Suraj
2026-01-06 11:20   ` Shankar, Uma
2026-01-07  0:04   ` Alex Hung
2025-12-19  6:56 ` [PATCH 11/13] drm/vkms: Remove drm_colorop_pipeline_destroy() from vkms_destroy() Chaitanya Kumar Borah
2026-01-06 11:21   ` Shankar, Uma
2025-12-19  6:56 ` [PATCH 12/13] drm/colorop: Use destroy callback for color pipeline teardown Chaitanya Kumar Borah
2026-01-05  9:27   ` Kandpal, Suraj
2026-01-06 11:23   ` Shankar, Uma
2026-01-07  0:05   ` Alex Hung [this message]
2025-12-19  6:56 ` [PATCH 13/13] drm/i915/color: Add failure handling in plane color pipeline init Chaitanya Kumar Borah
2026-01-06  3:55   ` Kandpal, Suraj
2026-01-06 11:57     ` Shankar, Uma
2026-01-09  8:49     ` Borah, Chaitanya Kumar

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=924e88fe-e2ff-4faf-8800-a056ef775599@amd.com \
    --to=alex.hung@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=chaitanya.kumar.borah@intel.com \
    --cc=contact@emersion.fr \
    --cc=daniels@collabora.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=harry.wentland@amd.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=louis.chauvet@bootlin.com \
    --cc=matthew.d.roper@intel.com \
    --cc=mwen@igalia.com \
    --cc=nfraprado@collabora.com \
    --cc=suraj.kandpal@intel.com \
    --cc=uma.shankar@intel.com \
    --cc=ville.syrjala@linux.intel.com \
    /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