From: Matthew Auld <matthew.auld@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: [Intel-xe] [PATCH 1/2] drm/xe/ct: fix resv_space print
Date: Wed, 23 Aug 2023 18:55:52 +0100 [thread overview]
Message-ID: <20230823175551.230686-3-matthew.auld@intel.com> (raw)
Actually print the info.resv_space.
Signed-off-by: Matthew Auld <matthew.auld@intel.com>
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
---
drivers/gpu/drm/xe/xe_guc_ct.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/xe/xe_guc_ct.c b/drivers/gpu/drm/xe/xe_guc_ct.c
index 59136b6a7c6f..b92e04ba8f63 100644
--- a/drivers/gpu/drm/xe/xe_guc_ct.c
+++ b/drivers/gpu/drm/xe/xe_guc_ct.c
@@ -1180,7 +1180,7 @@ static void guc_ctb_snapshot_print(struct guc_ctb_snapshot *snapshot,
u32 head, tail;
drm_printf(p, "\tsize: %d\n", snapshot->info.size);
- drm_printf(p, "\tresv_space: %d\n", snapshot->info.space);
+ drm_printf(p, "\tresv_space: %d\n", snapshot->info.resv_space);
drm_printf(p, "\thead: %d\n", snapshot->info.head);
drm_printf(p, "\ttail: %d\n", snapshot->info.tail);
drm_printf(p, "\tspace: %d\n", snapshot->info.space);
--
2.41.0
next reply other threads:[~2023-08-23 17:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-23 17:55 Matthew Auld [this message]
2023-08-23 17:55 ` [Intel-xe] [PATCH 2/2] drm/xe: nuke GuC on unload Matthew Auld
2023-08-24 14:26 ` Matthew Brost
2023-08-24 15:19 ` Matthew Auld
2023-08-23 18:00 ` [Intel-xe] ✓ CI.Patch_applied: success for series starting with [1/2] drm/xe/ct: fix resv_space print Patchwork
2023-08-23 18:00 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-08-23 18:01 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-08-23 18:05 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-08-23 18:06 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-08-23 18:06 ` [Intel-xe] ✗ CI.checksparse: warning " Patchwork
2023-08-23 18:32 ` [Intel-xe] ✓ CI.BAT: success " Patchwork
2023-08-24 14:17 ` [Intel-xe] [PATCH 1/2] " 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=20230823175551.230686-3-matthew.auld@intel.com \
--to=matthew.auld@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=rodrigo.vivi@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