Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Brost <matthew.brost@intel.com>
To: Nirmoy Das <nirmoy.das@intel.com>
Cc: <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH] drm/xe: Remove uninitialized end var from xe_gt_tlb_invalidation_range()
Date: Mon, 29 Apr 2024 19:33:46 +0000	[thread overview]
Message-ID: <Zi/2God6Cc0BzNwH@DUT025-TGLU.fm.intel.com> (raw)
In-Reply-To: <20240429152821.27490-1-nirmoy.das@intel.com>

On Mon, Apr 29, 2024 at 05:28:21PM +0200, Nirmoy Das wrote:
> This fixes commit c4f18703629d ("drm/xe: Add
> xe_gt_tlb_invalidation_range and convert PT layer to use this")
> which added the end variable as part of the function param.
> 

Good catch, thanks. I think this needs a proper fixes tag:

Fixes: c4f18703629d ("drm/xe: Add xe_gt_tlb_invalidation_range and convert PT layer to use this")

With the new tag:
Reviewed-by: Matthew Brost <matthew.brost@intel.com>

> Cc: Matthew Brost <matthew.brost@intel.com>
> Signed-off-by: Nirmoy Das <nirmoy.das@intel.com>
> ---
>  drivers/gpu/drm/xe/xe_gt_tlb_invalidation.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/xe/xe_gt_tlb_invalidation.c b/drivers/gpu/drm/xe/xe_gt_tlb_invalidation.c
> index d0ee1e0df0bd..c3d015a7ac33 100644
> --- a/drivers/gpu/drm/xe/xe_gt_tlb_invalidation.c
> +++ b/drivers/gpu/drm/xe/xe_gt_tlb_invalidation.c
> @@ -305,7 +305,7 @@ int xe_gt_tlb_invalidation_range(struct xe_gt *gt,
>  	} else {
>  		u64 orig_start = start;
>  		u64 length = end - start;
> -		u64 align, end;
> +		u64 align;
>  
>  		if (length < SZ_4K)
>  			length = SZ_4K;
> -- 
> 2.42.0
> 

      parent reply	other threads:[~2024-04-29 19:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-29 15:28 [PATCH] drm/xe: Remove uninitialized end var from xe_gt_tlb_invalidation_range() Nirmoy Das
2024-04-29 15:48 ` ✓ CI.Patch_applied: success for " Patchwork
2024-04-29 15:48 ` ✓ CI.checkpatch: " Patchwork
2024-04-29 15:49 ` ✓ CI.KUnit: " Patchwork
2024-04-29 19:33 ` Matthew Brost [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=Zi/2God6Cc0BzNwH@DUT025-TGLU.fm.intel.com \
    --to=matthew.brost@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=nirmoy.das@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