Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Roper <matthew.d.roper@intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: intel-xe@lists.freedesktop.org,
	"Priyanka Dandamudi" <priyanka.dandamudi@intel.com>,
	"Oak Zeng" <oak.zeng@intel.com>,
	"Thomas Hellström" <thomas.hellstrom@linux.intel.com>
Subject: Re: [PATCH] drm/xe: Fix cast on trace variable again
Date: Tue, 20 Feb 2024 14:54:30 -0800	[thread overview]
Message-ID: <20240220225430.GE5347@mdroper-desk1.amr.corp.intel.com> (raw)
In-Reply-To: <20240220205607.1873084-1-lucas.demarchi@intel.com>

On Tue, Feb 20, 2024 at 12:56:07PM -0800, Lucas De Marchi wrote:
> Same fix as commit 8d038f49c1f3 ("drm/xe: Fix cast on trace variable")
> that has been inadvertently reverted by a later commit.
> 
> Fixes: a0df2cc858c3 ("drm/xe/xe_bo_move: Enhance xe_bo_move trace")
> Cc: Matt Roper <matthew.d.roper@intel.com>
> Cc: Priyanka Dandamudi <priyanka.dandamudi@intel.com>
> Cc: Oak Zeng <oak.zeng@intel.com>
> Cc: Thomas Hellström <thomas.hellstrom@linux.intel.com>
> Signed-off-by: Lucas De Marchi <lucas.demarchi@intel.com>

Reviewed-by: Matt Roper <matthew.d.roper@intel.com>

> ---
>  drivers/gpu/drm/xe/xe_trace.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/xe/xe_trace.h b/drivers/gpu/drm/xe/xe_trace.h
> index 0cce98a6b14b..e43c3bde3202 100644
> --- a/drivers/gpu/drm/xe/xe_trace.h
> +++ b/drivers/gpu/drm/xe/xe_trace.h
> @@ -32,7 +32,7 @@ DECLARE_EVENT_CLASS(xe_gt_tlb_invalidation_fence,
>  			     ),
>  
>  		    TP_fast_assign(
> -			   __entry->fence = (u64)fence;
> +			   __entry->fence = (unsigned long)fence;
>  			   __entry->seqno = fence->seqno;
>  			   ),
>  
> -- 
> 2.43.0
> 

-- 
Matt Roper
Graphics Software Engineer
Linux GPU Platform Enablement
Intel Corporation

  parent reply	other threads:[~2024-02-20 22:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-20 20:56 [PATCH] drm/xe: Fix cast on trace variable again Lucas De Marchi
2024-02-20 21:11 ` ✓ CI.Patch_applied: success for " Patchwork
2024-02-20 21:12 ` ✓ CI.checkpatch: " Patchwork
2024-02-20 21:12 ` ✓ CI.KUnit: " Patchwork
2024-02-20 21:23 ` ✓ CI.Build: " Patchwork
2024-02-20 21:24 ` ✓ CI.Hooks: " Patchwork
2024-02-20 21:25 ` ✓ CI.checksparse: " Patchwork
2024-02-20 21:49 ` ✓ CI.BAT: " Patchwork
2024-02-20 22:54 ` Matt Roper [this message]
2024-02-21 17:58 ` [PATCH] " Ville Syrjälä
2024-02-21 20:20   ` Lucas De Marchi
2024-02-21 20:25 ` ✗ CI.Patch_applied: failure for drm/xe: Fix cast on trace variable again (rev2) 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=20240220225430.GE5347@mdroper-desk1.amr.corp.intel.com \
    --to=matthew.d.roper@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=lucas.demarchi@intel.com \
    --cc=oak.zeng@intel.com \
    --cc=priyanka.dandamudi@intel.com \
    --cc=thomas.hellstrom@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