intel-xe.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: Re: [RESEND 5/5] drm/i915/plane: rename intel_atomic_add_affected_planes() to intel_plane_add_affected()
Date: Fri, 13 Jun 2025 18:02:21 +0300	[thread overview]
Message-ID: <aEw9fc3XSfaoxCGV@intel.com> (raw)
In-Reply-To: <88e5eff2556e6363e51cbe4d2143fa0817d3c00d.1749728173.git.jani.nikula@intel.com>

On Thu, Jun 12, 2025 at 02:37:11PM +0300, Jani Nikula wrote:
> Rename to follow filename based naming.
> 
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
> ---
>  drivers/gpu/drm/i915/display/intel_display.c | 4 ++--
>  drivers/gpu/drm/i915/display/intel_plane.c   | 4 ++--
>  drivers/gpu/drm/i915/display/intel_plane.h   | 4 ++--
>  3 files changed, 6 insertions(+), 6 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/display/intel_display.c b/drivers/gpu/drm/i915/display/intel_display.c
> index bd81ff9e3854..978c524546c6 100644
> --- a/drivers/gpu/drm/i915/display/intel_display.c
> +++ b/drivers/gpu/drm/i915/display/intel_display.c
> @@ -5479,7 +5479,7 @@ static int intel_modeset_pipe(struct intel_atomic_state *state,
>  	if (ret)
>  		return ret;
>  
> -	ret = intel_atomic_add_affected_planes(state, crtc);
> +	ret = intel_plane_add_affected(state, crtc);

This breaks the common naming pattern. At the very least I think
it needs to keep the "planes" at the end to make it clear what
it's adding.

But from the "does this sentence make any sense?" POV I'd
rather it be called intel_crtc_add_affected_planes().

>  	if (ret)
>  		return ret;
>  
> @@ -6195,7 +6195,7 @@ static int intel_joiner_add_affected_crtcs(struct intel_atomic_state *state)
>  		if (ret)
>  			return ret;
>  
> -		ret = intel_atomic_add_affected_planes(state, crtc);
> +		ret = intel_plane_add_affected(state, crtc);
>  		if (ret)
>  			return ret;
>  	}
> diff --git a/drivers/gpu/drm/i915/display/intel_plane.c b/drivers/gpu/drm/i915/display/intel_plane.c
> index 2ac7a4e655f5..11aeb7435b05 100644
> --- a/drivers/gpu/drm/i915/display/intel_plane.c
> +++ b/drivers/gpu/drm/i915/display/intel_plane.c
> @@ -1433,8 +1433,8 @@ static int intel_crtc_add_planes_to_state(struct intel_atomic_state *state,
>  	return 0;
>  }
>  
> -int intel_atomic_add_affected_planes(struct intel_atomic_state *state,
> -				     struct intel_crtc *crtc)
> +int intel_plane_add_affected(struct intel_atomic_state *state,
> +			     struct intel_crtc *crtc)
>  {
>  	const struct intel_crtc_state *old_crtc_state =
>  		intel_atomic_get_old_crtc_state(state, crtc);
> diff --git a/drivers/gpu/drm/i915/display/intel_plane.h b/drivers/gpu/drm/i915/display/intel_plane.h
> index 5cb995b2940f..4ef012c08fa4 100644
> --- a/drivers/gpu/drm/i915/display/intel_plane.h
> +++ b/drivers/gpu/drm/i915/display/intel_plane.h
> @@ -83,8 +83,8 @@ void intel_plane_helper_add(struct intel_plane *plane);
>  bool intel_plane_needs_physical(struct intel_plane *plane);
>  void intel_plane_init_cursor_vblank_work(struct intel_plane_state *old_plane_state,
>  					 struct intel_plane_state *new_plane_state);
> -int intel_atomic_add_affected_planes(struct intel_atomic_state *state,
> -				     struct intel_crtc *crtc);
> +int intel_plane_add_affected(struct intel_atomic_state *state,
> +			     struct intel_crtc *crtc);
>  int intel_plane_atomic_check(struct intel_atomic_state *state);
>  
>  u32 intel_plane_ggtt_offset(const struct intel_plane_state *plane_state);
> -- 
> 2.39.5

-- 
Ville Syrjälä
Intel

  parent reply	other threads:[~2025-06-13 15:02 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-12 11:37 [RESEND 0/5] drm/i915/plane: file and function renames Jani Nikula
2025-06-12 11:37 ` [RESEND 1/5] drm/i915/plane: rename intel_atomic_plane.[ch] to intel_plane.[ch] Jani Nikula
2025-06-12 12:22   ` Gustavo Sousa
2025-06-12 15:20   ` [PATCH v2] " Jani Nikula
2025-06-12 11:37 ` [RESEND 2/5] drm/i915/plane: drop atomic from intel_atomic_plane_check_clipping() Jani Nikula
2025-06-12 12:23   ` Gustavo Sousa
2025-06-12 11:37 ` [RESEND 3/5] drm/i915/plane: make intel_plane_atomic_check() static and rename Jani Nikula
2025-06-12 12:14   ` Gustavo Sousa
2025-06-12 11:37 ` [RESEND 4/5] drm/i915/plane: rename intel_atomic_check_planes() to intel_plane_atomic_check() Jani Nikula
2025-06-12 12:23   ` Gustavo Sousa
2025-06-12 11:37 ` [RESEND 5/5] drm/i915/plane: rename intel_atomic_add_affected_planes() to intel_plane_add_affected() Jani Nikula
2025-06-12 12:24   ` Gustavo Sousa
2025-06-13 15:02   ` Ville Syrjälä [this message]
2025-06-13 15:06     ` Ville Syrjälä
2025-06-12 11:55 ` ✗ CI.checkpatch: warning for drm/i915/plane: file and function renames (rev2) Patchwork
2025-06-12 11:56 ` ✓ CI.KUnit: success " Patchwork
2025-06-12 12:11 ` ✗ CI.checksparse: warning " Patchwork
2025-06-12 13:08 ` ✓ Xe.CI.BAT: success " Patchwork
2025-06-12 18:23 ` ✗ CI.checkpatch: warning for drm/i915/plane: file and function renames (rev3) Patchwork
2025-06-12 18:25 ` ✓ CI.KUnit: success " Patchwork
2025-06-12 18:40 ` ✗ CI.checksparse: warning " Patchwork
2025-06-12 19:51 ` ✓ Xe.CI.BAT: success " Patchwork
2025-06-13  0:07 ` ✗ Xe.CI.Full: failure for drm/i915/plane: file and function renames (rev2) Patchwork
2025-06-13 10:08 ` ✗ Xe.CI.Full: failure for drm/i915/plane: file and function renames (rev3) Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2025-06-17  8:13 [RESEND 0/5] drm/i915/plane: file and function renames Jani Nikula
2025-06-17  8:13 ` [RESEND 5/5] drm/i915/plane: rename intel_atomic_add_affected_planes() to intel_plane_add_affected() Jani Nikula

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=aEw9fc3XSfaoxCGV@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jani.nikula@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;
as well as URLs for NNTP newsgroup(s).