All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	dri-devel@lists.freedesktop.org, amd-gfx@lists.freedesktop.org,
	Daniel Vetter <daniel@ffwll.ch>, David Airlie <airlied@gmail.com>,
	Hamza Mahfooz <hamza.mahfooz@amd.com>
Subject: Re: [PATCH v2] drm: Spelling s/sempahore/semaphore/
Date: Mon, 17 Jul 2023 10:59:30 -0400	[thread overview]
Message-ID: <ZLVXUlZJO/cuT4Jw@intel.com> (raw)
In-Reply-To: <8b0542c12a2427f34a792c41ac2d2a2922874bfa.1689600102.git.geert+renesas@glider.be>

On Mon, Jul 17, 2023 at 03:23:20PM +0200, Geert Uytterhoeven wrote:
> Fix misspellings of "semaphore".
> 
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> Reviewed-by: Hamza Mahfooz <hamza.mahfooz@amd.com>
> ---
> v2:
>   - Add Reviewed-by.
> ---
>  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 894068bb37b6f1b6..32323bb801a139b7 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)


Acked-by: Rodrigo Vivi <rodrigo.vivi@intel.com>

to take this through drm-misc

> 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 382795a8b3c064ba..a17b95eec65fb810 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/
>   */
>  
>  
> -- 
> 2.34.1
> 

WARNING: multiple messages have this Message-ID (diff)
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	dri-devel@lists.freedesktop.org, amd-gfx@lists.freedesktop.org,
	Daniel Vetter <daniel@ffwll.ch>, David Airlie <airlied@gmail.com>,
	Hamza Mahfooz <hamza.mahfooz@amd.com>
Subject: Re: [Intel-gfx] [PATCH v2] drm: Spelling s/sempahore/semaphore/
Date: Mon, 17 Jul 2023 10:59:30 -0400	[thread overview]
Message-ID: <ZLVXUlZJO/cuT4Jw@intel.com> (raw)
In-Reply-To: <8b0542c12a2427f34a792c41ac2d2a2922874bfa.1689600102.git.geert+renesas@glider.be>

On Mon, Jul 17, 2023 at 03:23:20PM +0200, Geert Uytterhoeven wrote:
> Fix misspellings of "semaphore".
> 
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> Reviewed-by: Hamza Mahfooz <hamza.mahfooz@amd.com>
> ---
> v2:
>   - Add Reviewed-by.
> ---
>  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 894068bb37b6f1b6..32323bb801a139b7 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)


Acked-by: Rodrigo Vivi <rodrigo.vivi@intel.com>

to take this through drm-misc

> 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 382795a8b3c064ba..a17b95eec65fb810 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/
>   */
>  
>  
> -- 
> 2.34.1
> 

WARNING: multiple messages have this Message-ID (diff)
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	dri-devel@lists.freedesktop.org, amd-gfx@lists.freedesktop.org,
	Hamza Mahfooz <hamza.mahfooz@amd.com>
Subject: Re: [PATCH v2] drm: Spelling s/sempahore/semaphore/
Date: Mon, 17 Jul 2023 10:59:30 -0400	[thread overview]
Message-ID: <ZLVXUlZJO/cuT4Jw@intel.com> (raw)
In-Reply-To: <8b0542c12a2427f34a792c41ac2d2a2922874bfa.1689600102.git.geert+renesas@glider.be>

On Mon, Jul 17, 2023 at 03:23:20PM +0200, Geert Uytterhoeven wrote:
> Fix misspellings of "semaphore".
> 
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> Reviewed-by: Hamza Mahfooz <hamza.mahfooz@amd.com>
> ---
> v2:
>   - Add Reviewed-by.
> ---
>  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 894068bb37b6f1b6..32323bb801a139b7 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)


Acked-by: Rodrigo Vivi <rodrigo.vivi@intel.com>

to take this through drm-misc

> 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 382795a8b3c064ba..a17b95eec65fb810 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/
>   */
>  
>  
> -- 
> 2.34.1
> 

WARNING: multiple messages have this Message-ID (diff)
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
	<intel-gfx@lists.freedesktop.org>,
	Hamza Mahfooz <hamza.mahfooz@amd.com>,
	<amd-gfx@lists.freedesktop.org>,
	<dri-devel@lists.freedesktop.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] drm: Spelling s/sempahore/semaphore/
Date: Mon, 17 Jul 2023 10:59:30 -0400	[thread overview]
Message-ID: <ZLVXUlZJO/cuT4Jw@intel.com> (raw)
In-Reply-To: <8b0542c12a2427f34a792c41ac2d2a2922874bfa.1689600102.git.geert+renesas@glider.be>

On Mon, Jul 17, 2023 at 03:23:20PM +0200, Geert Uytterhoeven wrote:
> Fix misspellings of "semaphore".
> 
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> Reviewed-by: Hamza Mahfooz <hamza.mahfooz@amd.com>
> ---
> v2:
>   - Add Reviewed-by.
> ---
>  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 894068bb37b6f1b6..32323bb801a139b7 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)


Acked-by: Rodrigo Vivi <rodrigo.vivi@intel.com>

to take this through drm-misc

> 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 382795a8b3c064ba..a17b95eec65fb810 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/
>   */
>  
>  
> -- 
> 2.34.1
> 

  reply	other threads:[~2023-07-17 14:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-17 13:23 [PATCH v2] drm: Spelling s/sempahore/semaphore/ Geert Uytterhoeven
2023-07-17 13:23 ` Geert Uytterhoeven
2023-07-17 13:23 ` [Intel-gfx] " Geert Uytterhoeven
2023-07-17 14:59 ` Rodrigo Vivi [this message]
2023-07-17 14:59   ` Rodrigo Vivi
2023-07-17 14:59   ` Rodrigo Vivi
2023-07-17 14:59   ` [Intel-gfx] " Rodrigo Vivi
2023-07-17 17:44 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2023-07-17 22:01 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2023-07-29 19:10 ` [PATCH v2] " Javier Martinez Canillas
2023-07-29 19:10   ` Javier Martinez Canillas
2023-07-29 19:10   ` [Intel-gfx] " Javier Martinez Canillas

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=ZLVXUlZJO/cuT4Jw@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=airlied@gmail.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=geert+renesas@glider.be \
    --cc=hamza.mahfooz@amd.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.