Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Hamza Mahfooz <hamza.mahfooz@amd.com>
To: "Geert Uytterhoeven" <geert+renesas@glider.be>,
	"Jani Nikula" <jani.nikula@linux.intel.com>,
	"Joonas Lahtinen" <joonas.lahtinen@linux.intel.com>,
	"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
	"Tvrtko Ursulin" <tvrtko.ursulin@linux.intel.com>,
	"David Airlie" <airlied@gmail.com>,
	"Daniel Vetter" <daniel@ffwll.ch>,
	"Alex Deucher" <alexander.deucher@amd.com>,
	"Christian König" <christian.koenig@amd.com>,
	Pan@rox.of.borg, Xinhui <Xinhui.Pan@amd.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	amd-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [Intel-gfx] [PATCH v2 1/2] drm: Spelling s/sempahore/semaphore/
Date: Tue, 11 Apr 2023 10:37:28 -0400	[thread overview]
Message-ID: <fe1c8197-545d-aaae-4352-d6fe3681b3ce@amd.com> (raw)
In-Reply-To: <50439958420f91cc97ad929437334bfb19ca4d90.1681210312.git.geert+renesas@glider.be>

On 4/11/23 06:52, Geert Uytterhoeven wrote:
> Fix misspellings of "semaphore".
> 
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>

Series is

Reviewed-by: Hamza Mahfooz <hamza.mahfooz@amd.com>

> ---
>   drivers/gpu/drm/i915/i915_request.c | 2 +-
>   drivers/gpu/drm/radeon/cik.c        | 2 +-
>   drivers/gpu/drm/radeon/r600.c       | 2 +-
>   include/drm/task_barrier.h          | 2 +-
>   4 files changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/i915_request.c b/drivers/gpu/drm/i915/i915_request.c
> index 630a732aaecca8fb..0bb368a5dd0bb107 100644
> --- a/drivers/gpu/drm/i915/i915_request.c
> +++ b/drivers/gpu/drm/i915/i915_request.c
> @@ -1220,7 +1220,7 @@ emit_semaphore_wait(struct i915_request *to,
>   	/*
>   	 * If this or its dependents are waiting on an external fence
>   	 * that may fail catastrophically, then we want to avoid using
> -	 * sempahores as they bypass the fence signaling metadata, and we
> +	 * semaphores as they bypass the fence signaling metadata, and we
>   	 * lose the fence->error propagation.
>   	 */
>   	if (from->sched.flags & I915_SCHED_HAS_EXTERNAL_CHAIN)
> diff --git a/drivers/gpu/drm/radeon/cik.c b/drivers/gpu/drm/radeon/cik.c
> index 5819737c21c678d3..5d6b81a6578ef2ba 100644
> --- a/drivers/gpu/drm/radeon/cik.c
> +++ b/drivers/gpu/drm/radeon/cik.c
> @@ -3603,7 +3603,7 @@ void cik_fence_compute_ring_emit(struct radeon_device *rdev,
>    * @rdev: radeon_device pointer
>    * @ring: radeon ring buffer object
>    * @semaphore: radeon semaphore object
> - * @emit_wait: Is this a sempahore wait?
> + * @emit_wait: Is this a semaphore wait?
>    *
>    * Emits a semaphore signal/wait packet to the CP ring and prevents the PFP
>    * from running ahead of semaphore waits.
> diff --git a/drivers/gpu/drm/radeon/r600.c b/drivers/gpu/drm/radeon/r600.c
> index dd78fc4994024815..34457e51035278fb 100644
> --- a/drivers/gpu/drm/radeon/r600.c
> +++ b/drivers/gpu/drm/radeon/r600.c
> @@ -2918,7 +2918,7 @@ void r600_fence_ring_emit(struct radeon_device *rdev,
>    * @rdev: radeon_device pointer
>    * @ring: radeon ring buffer object
>    * @semaphore: radeon semaphore object
> - * @emit_wait: Is this a sempahore wait?
> + * @emit_wait: Is this a semaphore wait?
>    *
>    * Emits a semaphore signal/wait packet to the CP ring and prevents the PFP
>    * from running ahead of semaphore waits.
> diff --git a/include/drm/task_barrier.h b/include/drm/task_barrier.h
> index 087e3f649c52f02d..217c1cf21c1ab7d5 100644
> --- a/include/drm/task_barrier.h
> +++ b/include/drm/task_barrier.h
> @@ -25,7 +25,7 @@
>   
>   /*
>    * Reusable 2 PHASE task barrier (randevouz point) implementation for N tasks.
> - * Based on the Little book of sempahores - https://greenteapress.com/wp/semaphores/
> + * Based on the Little book of semaphores - https://greenteapress.com/wp/semaphores/
>    */
>   
>   
-- 
Hamza


  parent reply	other threads:[~2023-04-11 14:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-11 10:52 [Intel-gfx] [PATCH v2 1/2] drm: Spelling s/sempahore/semaphore/ Geert Uytterhoeven
2023-04-11 10:52 ` [Intel-gfx] [PATCH v2 2/2] drm: Spelling s/randevouz/rendez-vous/ Geert Uytterhoeven
2023-04-11 14:37 ` Hamza Mahfooz [this message]
2023-04-11 21:58 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for series starting with [v2,1/2] drm: Spelling s/sempahore/semaphore/ Patchwork
2023-04-11 22:11 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-04-12 12:41 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork

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=fe1c8197-545d-aaae-4352-d6fe3681b3ce@amd.com \
    --to=hamza.mahfooz@amd.com \
    --cc=Pan@rox.of.borg \
    --cc=Xinhui.Pan@amd.com \
    --cc=airlied@gmail.com \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=christian.koenig@amd.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=geert+renesas@glider.be \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rodrigo.vivi@intel.com \
    --cc=tvrtko.ursulin@linux.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