Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: John.C.Harrison@Intel.com
To: Intel-Xe@Lists.FreeDesktop.Org
Cc: John Harrison <John.C.Harrison@Intel.com>,
	Michal Wajdeczko <michal.wajdeczko@intel.com>
Subject: [PATCH v4 1/4] drm/xe/guc: Remove double blank line
Date: Mon, 12 May 2025 14:53:21 -0700	[thread overview]
Message-ID: <20250512215324.1457009-2-John.C.Harrison@Intel.com> (raw)
In-Reply-To: <20250512215324.1457009-1-John.C.Harrison@Intel.com>

From: John Harrison <John.C.Harrison@Intel.com>

An earlier patch moved a drm_print a few lines lower but accidentally
left a double blank line behind. So fix that.

Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
Reviewed-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
---
 drivers/gpu/drm/xe/xe_guc_ct.c | 1 -
 1 file changed, 1 deletion(-)

diff --git a/drivers/gpu/drm/xe/xe_guc_ct.c b/drivers/gpu/drm/xe/xe_guc_ct.c
index ff6edf1b14f4..b09dd5788a27 100644
--- a/drivers/gpu/drm/xe/xe_guc_ct.c
+++ b/drivers/gpu/drm/xe/xe_guc_ct.c
@@ -2013,7 +2013,6 @@ static void ct_dead_print(struct xe_dead_ct *dead)
 		return;
 	}
 
-
 	/* Can't generate a genuine core dump at this point, so just do the good bits */
 	drm_puts(&lp, "**** Xe Device Coredump ****\n");
 	drm_printf(&lp, "Reason: CTB is dead - 0x%X\n", dead->reason);
-- 
2.49.0


  reply	other threads:[~2025-05-12 21:53 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-12 21:53 [PATCH v4 0/4] Track FAST_REQ H2Gs to report where errors came from John.C.Harrison
2025-05-12 21:53 ` John.C.Harrison [this message]
2025-05-12 21:53 ` [PATCH v4 2/4] drm/xe/guc: Add missing H2G error code definitions John.C.Harrison
2025-05-12 21:53 ` [PATCH v4 3/4] drm/xe/guc: Rename CONFIG_XE_LARGE_GUC_BUFFER John.C.Harrison
2025-05-12 21:53 ` [PATCH v4 4/4] drm/xe/guc: Track FAST_REQ H2Gs to report where errors came from John.C.Harrison
2025-05-12 21:58 ` ✓ CI.Patch_applied: success for " Patchwork
2025-05-12 21:59 ` ✗ CI.checkpatch: warning " Patchwork
2025-05-12 22:00 ` ✓ CI.KUnit: success " Patchwork
2025-05-12 22:10 ` ✗ CI.Build: failure " Patchwork
2025-05-13 14:07 ` ✓ CI.Patch_applied: success " Patchwork
2025-05-13 14:08 ` ✗ CI.checkpatch: warning " Patchwork
2025-05-13 14:09 ` ✓ CI.KUnit: success " Patchwork
2025-05-13 14:19 ` ✓ CI.Build: " Patchwork
2025-05-14 18:07 ` ✓ CI.Patch_applied: success for Track FAST_REQ H2Gs to report where errors came from (rev2) Patchwork
2025-05-14 18:07 ` ✗ CI.checkpatch: warning " Patchwork
2025-05-14 18:08 ` ✓ CI.KUnit: success " Patchwork
2025-05-14 18:19 ` ✓ CI.Build: " Patchwork
2025-05-14 18:21 ` ✓ CI.Hooks: " Patchwork
2025-05-14 18:23 ` ✓ CI.checksparse: " Patchwork
2025-05-14 18:46 ` ✓ Xe.CI.BAT: " Patchwork
2025-05-15  2:10 ` ✗ Xe.CI.Full: failure " Patchwork
2025-05-27  0:44 ` ✗ CI.Patch_applied: " 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=20250512215324.1457009-2-John.C.Harrison@Intel.com \
    --to=john.c.harrison@intel.com \
    --cc=Intel-Xe@Lists.FreeDesktop.Org \
    --cc=michal.wajdeczko@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