From: Jani Nikula <jani.nikula@linux.intel.com>
To: Hemanth Selam <hemanth.selam@gmail.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Tvrtko Ursulin <tursulin@ursulin.net>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Zhenyu Wang <zhenyuw.linux@gmail.com>,
Zhi Wang <zhi.wang.linux@gmail.com>
Cc: linux-kernel@vger.kernel.org, intel-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 2/2] drm/i915: fix repeated words in comments
Date: Fri, 04 Sep 2026 15:12:19 +0300 [thread overview]
Message-ID: <4e651b9a124c47f5cbd07aee56f683c22252f172@intel.com> (raw)
In-Reply-To: <20260904120225.15868-3-hemanth.selam@gmail.com>
On Fri, 04 Sep 2026, Hemanth Selam <hemanth.selam@gmail.com> 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@gmail.com>
Reviewed-by: Jani Nikula <jani.nikula@intel.com>
> ---
> 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
prev parent reply other threads:[~2026-09-04 12:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 12:02 [PATCH 0/2] drm/i915: fix typos and " Hemanth Selam
2026-09-04 12:02 ` [PATCH 1/2] drm/i915: fix typos " Hemanth Selam
2026-09-04 12:12 ` Jani Nikula
2026-09-04 12:02 ` [PATCH 2/2] drm/i915: fix repeated words " Hemanth Selam
2026-09-04 12:12 ` Jani Nikula [this message]
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=4e651b9a124c47f5cbd07aee56f683c22252f172@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hemanth.selam@gmail.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=simona@ffwll.ch \
--cc=tursulin@ursulin.net \
--cc=zhenyuw.linux@gmail.com \
--cc=zhi.wang.linux@gmail.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
all inboxes | Powered by JetHome®