Re: [PATCH 2/2] drm/i915: fix repeated words in comments

[Jani Nikula]

On Fri, 04 Sep 2026, Hemanth Selam <hemanth.selam@xxxxxxxxx> wrote:
> Drop words accidentally written twice, reported by checkpatch.pl as a
> possible repeated word.  Only touches comments, no code changes.
>
> Assisted-by: Cursor:claude-opus-5
> Signed-off-by: Hemanth Selam <hemanth.selam@xxxxxxxxx>

Reviewed-by: Jani Nikula <jani.nikula@xxxxxxxxx>

> ---
>  drivers/gpu/drm/i915/gem/i915_gem_context_types.h | 2 +-
>  drivers/gpu/drm/i915/gt/uc/intel_guc.c            | 2 +-
>  drivers/gpu/drm/i915/gvt/scheduler.c              | 2 +-
>  drivers/gpu/drm/i915/i915_gem_evict.c             | 2 +-
>  4 files changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/gem/i915_gem_context_types.h b/drivers/gpu/drm/i915/gem/i915_gem_context_types.h
> index 0267c924634b..2c1f81d9c0d7 100644
> --- a/drivers/gpu/drm/i915/gem/i915_gem_context_types.h
> +++ b/drivers/gpu/drm/i915/gem/i915_gem_context_types.h
> @@ -208,7 +208,7 @@ struct i915_gem_proto_context {
>  	/** @legacy_rcs_sseu: Client-set SSEU parameters for the legacy RCS */
>  	struct intel_sseu legacy_rcs_sseu;
>  
> -	/** @single_timeline: See See &i915_gem_context.syncobj */
> +	/** @single_timeline: See &i915_gem_context.syncobj */
>  	bool single_timeline;
>  
>  	/** @uses_protected_content: See &i915_gem_context.uses_protected_content */
> diff --git a/drivers/gpu/drm/i915/gt/uc/intel_guc.c b/drivers/gpu/drm/i915/gt/uc/intel_guc.c
> index 1c2764440323..c007faa54f2d 100644
> --- a/drivers/gpu/drm/i915/gt/uc/intel_guc.c
> +++ b/drivers/gpu/drm/i915/gt/uc/intel_guc.c
> @@ -769,7 +769,7 @@ int intel_guc_resume(struct intel_guc *guc)
>   * This is a wrapper to create an object for use with the GuC. In order to
>   * use it inside the GuC, an object needs to be pinned lifetime, so we allocate
>   * both some backing storage and a range inside the Global GTT. We must pin
> - * it in the GGTT somewhere other than than [0, GUC ggtt_pin_bias) because that
> + * it in the GGTT somewhere other than [0, GUC ggtt_pin_bias) because that
>   * range is reserved inside GuC.
>   *
>   * Return:	A i915_vma if successful, otherwise an ERR_PTR.
> diff --git a/drivers/gpu/drm/i915/gvt/scheduler.c b/drivers/gpu/drm/i915/gvt/scheduler.c
> index 15fdd514ca83..3c3c9b695487 100644
> --- a/drivers/gpu/drm/i915/gvt/scheduler.c
> +++ b/drivers/gpu/drm/i915/gvt/scheduler.c
> @@ -201,7 +201,7 @@ static int populate_shadow_context(struct intel_vgpu_workload *workload)
>  			workload->ring_context_gpa);
>  
>  	/* only need to ensure this context is not pinned/unpinned during the
> -	 * period from last submission to this this submission.
> +	 * period from last submission to this submission.
>  	 * Upon reaching this function, the currently submitted context is not
>  	 * supposed to get unpinned. If a misbehaving guest driver ever does
>  	 * this, it would corrupt itself.
> diff --git a/drivers/gpu/drm/i915/i915_gem_evict.c b/drivers/gpu/drm/i915/i915_gem_evict.c
> index c02ebd6900ae..11855d9a1210 100644
> --- a/drivers/gpu/drm/i915/i915_gem_evict.c
> +++ b/drivers/gpu/drm/i915/i915_gem_evict.c
> @@ -273,7 +273,7 @@ i915_gem_evict_something(struct i915_address_space *vm,
>  	goto search_again;
>  
>  found:
> -	/* drm_mm doesn't allow any other other operations while
> +	/* drm_mm doesn't allow any other operations while
>  	 * scanning, therefore store to-be-evicted objects on a
>  	 * temporary list and take a reference for all before
>  	 * calling unbind (which may remove the active reference

-- 
Jani Nikula, Intel