From: sashiko-bot@kernel.org
To: "John Harrison" <John.Harrison@Igalia.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [RFC PATCH 1/8] drm/colorop: Reduce scope of colorop helpers
Date: Tue, 09 Jun 2026 17:31:02 +0000 [thread overview]
Message-ID: <20260609173102.7B1DD1F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260609171941.169104-2-John.Harrison@Igalia.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The prototype for `drm_atomic_set_colorop_for_plane` was not removed from the header file when the function was renamed and made static.
--
commit db8489fc6303b4a6973676321220c79b3ad4273f
Author: John Harrison <John.Harrison@Igalia.com>
drm/colorop: Reduce scope of colorop helpers
This commit reduces the scope of drm_colorop_find and
drm_atomic_set_colorop_for_plane by making them static local helpers within
the drm_atomic_uapi.c file.
> diff --git a/drivers/gpu/drm/drm_atomic_uapi.c b/drivers/gpu/drm/drm_atomic_uapi.c
> index 6441b55cc2740..530576850239f 100644
> --- a/drivers/gpu/drm/drm_atomic_uapi.c
> +++ b/drivers/gpu/drm/drm_atomic_uapi.c
[ ... ]
> @@ -259,16 +259,16 @@ drm_atomic_set_fb_for_plane(struct drm_plane_state *plane_state,
> EXPORT_SYMBOL(drm_atomic_set_fb_for_plane);
>
> /**
> - * drm_atomic_set_colorop_for_plane - set colorop for plane
> + * set_colorop_for_plane - set colorop for plane
> * @plane_state: atomic state object for the plane
> * @colorop: colorop to use for the plane
> *
> * Helper function to select the color pipeline on a plane by setting
> * it to the first drm_colorop element of the pipeline.
> */
> -void
> -drm_atomic_set_colorop_for_plane(struct drm_plane_state *plane_state,
> - struct drm_colorop *colorop)
> +static void
> +set_colorop_for_plane(struct drm_plane_state *plane_state,
> + struct drm_colorop *colorop)
[Severity: Low]
Since the exported function drm_atomic_set_colorop_for_plane is being renamed
and made static here, should its corresponding declaration in
include/drm/drm_atomic_uapi.h also be removed? The prototype remains in that
header file without an implementation, leaving a dangling declaration.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260609171941.169104-1-John.Harrison@Igalia.com?part=1
next prev parent reply other threads:[~2026-06-09 17:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-09 17:19 [RFC PATCH 0/8] Convert colorop pipelines to use proper lists John Harrison
2026-06-09 17:19 ` [RFC PATCH 1/8] drm/colorop: Reduce scope of colorop helpers John Harrison
2026-06-09 17:31 ` sashiko-bot [this message]
2026-06-09 17:19 ` [RFC PATCH 2/8] drm/colorop: Create pipelines via 'add to pipeline' instead of 'set next' John Harrison
2026-06-09 17:19 ` [RFC PATCH 3/8] drm/i915/colorop: Update to new pipeline API John Harrison
2026-06-09 17:32 ` sashiko-bot
2026-06-09 17:19 ` [RFC PATCH 4/8] drm/amd/colorop: " John Harrison
2026-06-09 17:37 ` sashiko-bot
2026-06-09 17:19 ` [RFC PATCH 5/8] drm/vkms/colorop: " John Harrison
2026-06-09 17:37 ` sashiko-bot
2026-06-09 17:19 ` [RFC PATCH 6/8] drm/colorop: Remove old add-next API as no longer used John Harrison
2026-06-09 17:19 ` [RFC PATCH 7/8] drm/colorop: Convert pipline 'next' pointer to a list John Harrison
2026-06-09 17:40 ` sashiko-bot
2026-06-09 17:19 ` [RFC PATCH 8/8] drm/colorop: Check that requested colorop is the root of a pipeline John Harrison
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=20260609173102.7B1DD1F00893@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=John.Harrison@Igalia.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=sashiko-reviews@lists.linux.dev \
/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