Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Julia Lawall <Julia.Lawall@inria.fr>
Cc: David Airlie <airlied@linux.ie>,
	intel-gfx@lists.freedesktop.org, kernel-janitors@vger.kernel.org,
	linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
	Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [Intel-gfx] [PATCH] drm/i915: fix typos in comments
Date: Tue, 24 May 2022 14:03:29 +0300	[thread overview]
Message-ID: <87ee0jw5tq.fsf@intel.com> (raw)
In-Reply-To: <20220521111145.81697-90-Julia.Lawall@inria.fr>

On Sat, 21 May 2022, Julia Lawall <Julia.Lawall@inria.fr> wrote:
> Spelling mistakes (triple letters) in comments.
> Detected with the help of Coccinelle.
>
> Signed-off-by: Julia Lawall <Julia.Lawall@inria.fr>

Thanks, pushed to drm-intel-next.

BR,
Jani.

>
> ---
>  drivers/gpu/drm/i915/display/intel_color.c           |    2 +-
>  drivers/gpu/drm/i915/display/intel_pps.c             |    2 +-
>  drivers/gpu/drm/i915/gt/intel_execlists_submission.c |    2 +-
>  drivers/gpu/drm/i915/gt/uc/intel_guc_log.c           |    2 +-
>  4 files changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_color.c b/drivers/gpu/drm/i915/display/intel_color.c
> index 34128c9c635c..a27ce874a9e8 100644
> --- a/drivers/gpu/drm/i915/display/intel_color.c
> +++ b/drivers/gpu/drm/i915/display/intel_color.c
> @@ -1638,7 +1638,7 @@ static u32 icl_gamma_mode(const struct intel_crtc_state *crtc_state)
>  	/*
>  	 * Enable 10bit gamma for D13
>  	 * ToDo: Extend to Logarithmic Gamma once the new UAPI
> -	 * is acccepted and implemented by a userspace consumer
> +	 * is accepted and implemented by a userspace consumer
>  	 */
>  	else if (DISPLAY_VER(i915) >= 13)
>  		gamma_mode |= GAMMA_MODE_MODE_10BIT;
> diff --git a/drivers/gpu/drm/i915/display/intel_pps.c b/drivers/gpu/drm/i915/display/intel_pps.c
> index 5a598dd06039..4bc0563dde92 100644
> --- a/drivers/gpu/drm/i915/display/intel_pps.c
> +++ b/drivers/gpu/drm/i915/display/intel_pps.c
> @@ -509,7 +509,7 @@ static void wait_panel_power_cycle(struct intel_dp *intel_dp)
>  
>  	drm_dbg_kms(&i915->drm, "Wait for panel power cycle\n");
>  
> -	/* take the difference of currrent time and panel power off time
> +	/* take the difference of current time and panel power off time
>  	 * and then make panel wait for t11_t12 if needed. */
>  	panel_power_on_time = ktime_get_boottime();
>  	panel_power_off_duration = ktime_ms_delta(panel_power_on_time, intel_dp->pps.panel_power_off_time);
> diff --git a/drivers/gpu/drm/i915/gt/intel_execlists_submission.c b/drivers/gpu/drm/i915/gt/intel_execlists_submission.c
> index 86f7a9ac1c39..aa0d2bbbbcc4 100644
> --- a/drivers/gpu/drm/i915/gt/intel_execlists_submission.c
> +++ b/drivers/gpu/drm/i915/gt/intel_execlists_submission.c
> @@ -1350,7 +1350,7 @@ static void execlists_dequeue(struct intel_engine_cs *engine)
>  			 * submission. If we don't cancel the timer now,
>  			 * we will see that the timer has expired and
>  			 * reschedule the tasklet; continually until the
> -			 * next context switch or other preeemption event.
> +			 * next context switch or other preemption event.
>  			 *
>  			 * Since we have decided to reschedule based on
>  			 * consumption of this timeslice, if we submit the
> diff --git a/drivers/gpu/drm/i915/gt/uc/intel_guc_log.c b/drivers/gpu/drm/i915/gt/uc/intel_guc_log.c
> index 78d2989fe917..02311ad90264 100644
> --- a/drivers/gpu/drm/i915/gt/uc/intel_guc_log.c
> +++ b/drivers/gpu/drm/i915/gt/uc/intel_guc_log.c
> @@ -588,7 +588,7 @@ int intel_guc_log_relay_open(struct intel_guc_log *log)
>  	/*
>  	 * We require SSE 4.1 for fast reads from the GuC log buffer and
>  	 * it should be present on the chipsets supporting GuC based
> -	 * submisssions.
> +	 * submissions.
>  	 */
>  	if (!i915_has_memcpy_from_wc()) {
>  		ret = -ENXIO;
>

-- 
Jani Nikula, Intel Open Source Graphics Center

      parent reply	other threads:[~2022-05-24 11:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-21 11:11 [Intel-gfx] [PATCH] drm/i915: fix typos in comments Julia Lawall
2022-05-24  7:47 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2022-05-24  8:57 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2022-05-24 11:03 ` 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=87ee0jw5tq.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=Julia.Lawall@inria.fr \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rodrigo.vivi@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