From: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
To: jose.souza@intel.com,
Lionel G Landwerlin <lionel.g.landwerlin@linux.intel.com>,
intel-xe@lists.freedesktop.org
Subject: [Intel-xe] [PATCH 2/3] drm/xe: Set the correct type for xe_to_user_engine_class
Date: Fri, 4 Aug 2023 14:32:52 -0700 [thread overview]
Message-ID: <20230804213253.2381705-3-umesh.nerlige.ramappa@intel.com> (raw)
In-Reply-To: <20230804213253.2381705-1-umesh.nerlige.ramappa@intel.com>
User engine class is of type u16. Set the same type for the array used to
map xe engines to user engines.
Signed-off-by: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
---
drivers/gpu/drm/xe/xe_query.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/xe/xe_query.c b/drivers/gpu/drm/xe/xe_query.c
index 297e93a0eb8c..99a4800c7c53 100644
--- a/drivers/gpu/drm/xe/xe_query.c
+++ b/drivers/gpu/drm/xe/xe_query.c
@@ -19,7 +19,7 @@
#include "xe_macros.h"
#include "xe_ttm_vram_mgr.h"
-static const enum xe_engine_class xe_to_user_engine_class[] = {
+static const u16 xe_to_user_engine_class[] = {
[XE_ENGINE_CLASS_RENDER] = DRM_XE_ENGINE_CLASS_RENDER,
[XE_ENGINE_CLASS_COPY] = DRM_XE_ENGINE_CLASS_COPY,
[XE_ENGINE_CLASS_VIDEO_DECODE] = DRM_XE_ENGINE_CLASS_VIDEO_DECODE,
--
2.38.1
next prev parent reply other threads:[~2023-08-04 21:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-04 21:32 [Intel-xe] [PATCH 0/3] Port CPU-GPU timestamp correlation to XE KMD Umesh Nerlige Ramappa
2023-08-04 21:32 ` [Intel-xe] [PATCH 1/3] drm/xe: Fix array bounds check for queries Umesh Nerlige Ramappa
2023-08-05 6:46 ` Niranjana Vishwanathapura
2023-08-04 21:32 ` Umesh Nerlige Ramappa [this message]
2023-08-05 6:54 ` [Intel-xe] [PATCH 2/3] drm/xe: Set the correct type for xe_to_user_engine_class Niranjana Vishwanathapura
2023-08-04 21:32 ` [Intel-xe] [PATCH 3/3] drm/xe: Correlate engine and cpu timestamps with better accuracy Umesh Nerlige Ramappa
2023-08-04 21:47 ` Umesh Nerlige Ramappa
2023-08-11 23:32 ` Dixit, Ashutosh
2023-08-12 0:30 ` Umesh Nerlige Ramappa
2023-08-12 0:32 ` Dixit, Ashutosh
2023-08-09 19:55 ` Souza, Jose
2023-08-09 20:18 ` Umesh Nerlige Ramappa
2023-08-04 22:38 ` [Intel-xe] ✓ CI.Patch_applied: success for Port CPU-GPU timestamp correlation to XE KMD Patchwork
2023-08-04 22:39 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-08-04 22:40 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-08-04 22:44 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-08-04 22:44 ` [Intel-xe] ✗ CI.Hooks: failure " 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=20230804213253.2381705-3-umesh.nerlige.ramappa@intel.com \
--to=umesh.nerlige.ramappa@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=jose.souza@intel.com \
--cc=lionel.g.landwerlin@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