Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Brost <matthew.brost@intel.com>
To: Francois Dugast <francois.dugast@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: Re: [Intel-xe] [PATCH 7/7] drm/xe: Fix typos
Date: Fri, 14 Jul 2023 14:23:18 +0000	[thread overview]
Message-ID: <ZLFaVs+5A4l4Vcqd@DUT025-TGLU> (raw)
In-Reply-To: <20230713150611.7-8-francois.dugast@intel.com>

On Thu, Jul 13, 2023 at 03:06:11PM +0000, Francois Dugast wrote:
> Fix minor issues: remove extra ';' and s/Initialise/Initialize/.
> 
> Signed-off-by: Francois Dugast <francois.dugast@intel.com>

Reviewed-by: Matthew Brost <matthew.brost@intel.com>

> ---
>  drivers/gpu/drm/xe/xe_guc.c | 2 +-
>  drivers/gpu/drm/xe/xe_vm.c  | 2 +-
>  2 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/gpu/drm/xe/xe_guc.c b/drivers/gpu/drm/xe/xe_guc.c
> index 8245bbc58770..ce8b35dcbc51 100644
> --- a/drivers/gpu/drm/xe/xe_guc.c
> +++ b/drivers/gpu/drm/xe/xe_guc.c
> @@ -200,7 +200,7 @@ static void guc_init_params(struct xe_guc *guc)
>  }
>  
>  /*
> - * Initialise the GuC parameter block before starting the firmware
> + * Initialize the GuC parameter block before starting the firmware
>   * transfer. These parameters are read by the firmware on startup
>   * and cannot be changed thereafter.
>   */
> diff --git a/drivers/gpu/drm/xe/xe_vm.c b/drivers/gpu/drm/xe/xe_vm.c
> index 6c216350084b..29bf8614c7dd 100644
> --- a/drivers/gpu/drm/xe/xe_vm.c
> +++ b/drivers/gpu/drm/xe/xe_vm.c
> @@ -3352,7 +3352,7 @@ int xe_vm_lock(struct xe_vm *vm, struct ww_acquire_ctx *ww,
>  	XE_BUG_ON(!ww);
>  
>  	tv_vm.num_shared = num_resv;
> -	tv_vm.bo = xe_vm_ttm_bo(vm);;
> +	tv_vm.bo = xe_vm_ttm_bo(vm);
>  	list_add_tail(&tv_vm.head, &objs);
>  
>  	return ttm_eu_reserve_buffers(ww, &objs, intr, &dups);
> -- 
> 2.34.1
> 

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

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-13 15:06 [Intel-xe] [PATCH 0/7] drm/xe: Code cleanup Francois Dugast
2023-07-13 15:06 ` [Intel-xe] [PATCH 1/7] drm/xe: Cleanup SPACING style issues Francois Dugast
2023-07-14 14:50   ` Matthew Brost
2023-07-13 15:06 ` [Intel-xe] [PATCH 2/7] drm/xe: Cleanup OPEN_BRACE " Francois Dugast
2023-07-14 14:10   ` Matthew Brost
2023-08-08 10:42     ` Jani Nikula
2023-07-13 15:06 ` [Intel-xe] [PATCH 3/7] drm/xe: Cleanup POINTER_LOCATION " Francois Dugast
2023-07-14 14:11   ` Matthew Brost
2023-07-13 15:06 ` [Intel-xe] [PATCH 4/7] drm/xe: Cleanup CODE_INDENT " Francois Dugast
2023-07-14 14:13   ` Matthew Brost
2023-07-13 15:06 ` [Intel-xe] [PATCH 5/7] drm/xe: Cleanup TRAILING_WHITESPACE " Francois Dugast
2023-07-14 14:22   ` Matthew Brost
2023-07-13 15:06 ` [Intel-xe] [PATCH 6/7] drm/xe: Cleanup COMPLEX_MACRO " Francois Dugast
2023-07-14 14:24   ` Matthew Brost
2023-07-13 15:06 ` [Intel-xe] [PATCH 7/7] drm/xe: Fix typos Francois Dugast
2023-07-14 14:23   ` Matthew Brost [this message]
2023-07-13 18:37 ` [Intel-xe] ✓ CI.Patch_applied: success for drm/xe: Code cleanup Patchwork
2023-07-13 18:37 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-07-13 18:38 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-07-13 18:42 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-07-13 18:43 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-07-13 18:44 ` [Intel-xe] ✓ CI.checksparse: " Patchwork
2023-07-13 20:33 ` [Intel-xe] [PATCH 0/7] " Rodrigo Vivi
2023-07-17  3:47   ` Lucas De Marchi
2023-08-08 10:47     ` Jani Nikula
2023-08-08 14:37       ` Lucas De Marchi
2023-08-08 15:05         ` Jani Nikula
2023-08-08 23:39           ` Lucas De Marchi
2023-08-09 15:30             ` Jani Nikula

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=ZLFaVs+5A4l4Vcqd@DUT025-TGLU \
    --to=matthew.brost@intel.com \
    --cc=francois.dugast@intel.com \
    --cc=intel-xe@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox