From: John.C.Harrison@Intel.com
To: Intel-Xe@Lists.FreeDesktop.Org
Cc: John Harrison <John.C.Harrison@Intel.com>
Subject: [PATCH 0/2] Clean up of GuC init data macros
Date: Wed, 11 Jun 2025 14:05:51 -0700 [thread overview]
Message-ID: <20250611210553.3756700-1-John.C.Harrison@Intel.com> (raw)
From: John Harrison <John.C.Harrison@Intel.com>
Code cleanups and add support for a debug feature.
Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
John Harrison (2):
drm/xe/guc: Clean up of GuC 'CTL' defines
drm/xe/guc: Add support for NPK as a GuC log target
drivers/gpu/drm/xe/xe_guc.c | 25 ++++++++++---------------
drivers/gpu/drm/xe/xe_guc_fwif.h | 28 +++++++++-------------------
drivers/gpu/drm/xe/xe_module.c | 4 ++++
drivers/gpu/drm/xe/xe_module.h | 1 +
4 files changed, 24 insertions(+), 34 deletions(-)
--
2.49.0
next reply other threads:[~2025-06-11 21:06 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-11 21:05 John.C.Harrison [this message]
2025-06-11 21:05 ` [PATCH 1/2] drm/xe/guc: Clean up of GuC 'CTL' defines John.C.Harrison
2025-06-11 22:04 ` Cavitt, Jonathan
2025-06-12 22:01 ` Lucas De Marchi
2025-06-11 21:05 ` [PATCH 2/2] drm/xe/guc: Add support for NPK as a GuC log target John.C.Harrison
2025-06-11 21:49 ` Lucas De Marchi
2025-06-11 23:51 ` John Harrison
2025-06-12 22:05 ` Lucas De Marchi
2025-06-12 23:43 ` John Harrison
2025-06-11 22:04 ` Cavitt, Jonathan
2025-06-11 23:57 ` John Harrison
2025-06-12 14:32 ` Cavitt, Jonathan
2025-06-12 17:49 ` John Harrison
2025-06-12 18:27 ` Cavitt, Jonathan
2025-06-12 18:47 ` John Harrison
2025-06-12 19:52 ` Cavitt, Jonathan
2025-06-12 19:30 ` Summers, Stuart
2025-06-11 21:11 ` ✓ CI.checkpatch: success for Clean up of GuC init data macros Patchwork
2025-06-11 21:12 ` ✓ CI.KUnit: " Patchwork
2025-06-11 21:23 ` ✓ CI.Build: " Patchwork
2025-06-11 21:25 ` ✓ CI.Hooks: " Patchwork
2025-06-11 21:27 ` ✓ CI.checksparse: " Patchwork
2025-06-11 22:19 ` ✓ Xe.CI.BAT: " Patchwork
2025-06-12 8:01 ` ✗ Xe.CI.Full: 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=20250611210553.3756700-1-John.C.Harrison@Intel.com \
--to=john.c.harrison@intel.com \
--cc=Intel-Xe@Lists.FreeDesktop.Org \
/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