public inbox for intel-xe@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Matthew Auld <matthew.auld@intel.com>
To: Xin Wang <x.wang@intel.com>, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH 1/2] drm/xe: Standardize pat_index to u16 type
Date: Tue, 7 Apr 2026 11:37:04 +0100	[thread overview]
Message-ID: <434ce3de-ea41-4019-b335-c97ee5f08b6a@intel.com> (raw)
In-Reply-To: <20260406182546.569131-2-x.wang@intel.com>

On 06/04/2026 19:25, Xin Wang wrote:
> Ensure all pat_index definitions consistently use u16 type across
> the XE driver. This addresses two remaining instances where pat_index
> was incorrectly typed:
> 
> - xe_vm_snapshot structure used int for pat_index field
> - xe_device pat.idx array used u32 instead of u16
> 
> This cleanup improves type consistency and ensures proper alignment
> with the PAT subsystem design.
> 
> Signed-off-by: Xin Wang <x.wang@intel.com>

Reviewed-by: Matthew Auld <matthew.auld@intel.com>


  reply	other threads:[~2026-04-07 10:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-06 18:25 [PATCH 0/2] drm/xe/pat: Type cleanup and invalid index hardening Xin Wang
2026-04-06 18:25 ` [PATCH 1/2] drm/xe: Standardize pat_index to u16 type Xin Wang
2026-04-07 10:37   ` Matthew Auld [this message]
2026-04-06 18:25 ` [PATCH 2/2] drm/xe/pat: Default XE_CACHE_NONE_COMPRESSION to invalid and assert on use Xin Wang
2026-04-07  9:48   ` Matthew Auld
2026-04-07 17:06     ` Wang, X
2026-04-06 18:32 ` ✓ CI.KUnit: success for drm/xe/pat: Type cleanup and invalid index hardening Patchwork
2026-04-06 19:07 ` ✓ Xe.CI.BAT: " Patchwork
2026-04-06 23:41 ` ✓ Xe.CI.FULL: " 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=434ce3de-ea41-4019-b335-c97ee5f08b6a@intel.com \
    --to=matthew.auld@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=x.wang@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