From: Matt Roper <matthew.d.roper@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: vinay.belgaumkar@intel.com, Matt Roper <matthew.d.roper@intel.com>
Subject: [PATCH] drm/xe: Update xe2_graphics name string
Date: Mon, 25 Nov 2024 11:48:39 -0800 [thread overview]
Message-ID: <20241125194838.1190599-2-matthew.d.roper@intel.com> (raw)
Since both Xe2 and Xe3 platforms currently use the same set of graphics
IP feature flags, we associate the "graphics_xe2" structure with both IPs.
Update the name string on that IP structure to clarify this and avoid
confusion as Xe3 platforms start going into public CI.
Fixes: 800d75bf20ae ("drm/xe/xe3: Define Xe3 feature flags")
Signed-off-by: Matt Roper <matthew.d.roper@intel.com>
---
drivers/gpu/drm/xe/xe_pci.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/xe/xe_pci.c b/drivers/gpu/drm/xe/xe_pci.c
index 9b81e7d00a86..7d146e3e8e21 100644
--- a/drivers/gpu/drm/xe/xe_pci.c
+++ b/drivers/gpu/drm/xe/xe_pci.c
@@ -174,7 +174,7 @@ static const struct xe_graphics_desc graphics_xelpg = {
GENMASK(XE_HW_ENGINE_CCS3, XE_HW_ENGINE_CCS0)
static const struct xe_graphics_desc graphics_xe2 = {
- .name = "Xe2_LPG / Xe2_HPG",
+ .name = "Xe2_LPG / Xe2_HPG / Xe3_LPG",
XE2_GFX_FEATURES,
};
--
2.47.0
next reply other threads:[~2024-11-25 19:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-25 19:48 Matt Roper [this message]
2024-11-25 19:53 ` [PATCH] drm/xe: Update xe2_graphics name string Belgaumkar, Vinay
2024-11-25 20:23 ` ✓ CI.Patch_applied: success for " Patchwork
2024-11-25 20:23 ` ✓ CI.checkpatch: " Patchwork
2024-11-25 20:26 ` ✓ CI.KUnit: " Patchwork
2024-11-25 20:48 ` ✓ CI.Build: " Patchwork
2024-11-25 20:51 ` ✓ CI.Hooks: " Patchwork
2024-11-25 20:52 ` ✓ CI.checksparse: " Patchwork
2024-11-25 21:10 ` ✓ Xe.CI.BAT: " Patchwork
2024-11-25 22:15 ` Matt Roper
2024-11-25 22:46 ` ✗ Xe.CI.Full: failure " Patchwork
2024-11-26 23:43 ` [PATCH] " Matthew Brost
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=20241125194838.1190599-2-matthew.d.roper@intel.com \
--to=matthew.d.roper@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=vinay.belgaumkar@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