Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: John.C.Harrison@Intel.com, Intel-Xe@Lists.FreeDesktop.Org
Subject: Re: [PATCH v3 1/4] drm/xe/guc: Remove double blank line
Date: Thu, 8 May 2025 21:37:39 +0200	[thread overview]
Message-ID: <e73487cb-eff4-449e-845b-5a55accd42e4@intel.com> (raw)
In-Reply-To: <20250508013437.652982-2-John.C.Harrison@Intel.com>



On 08.05.2025 03:34, John.C.Harrison@Intel.com wrote:
> 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 2447de0ebedf..9213fdc25950 100644
> --- a/drivers/gpu/drm/xe/xe_guc_ct.c
> +++ b/drivers/gpu/drm/xe/xe_guc_ct.c
> @@ -1830,7 +1830,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);


  reply	other threads:[~2025-05-08 19:37 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-08  1:34 [PATCH v3 0/4] Track FAST_REQ H2Gs to report where errors came from John.C.Harrison
2025-05-08  1:34 ` [PATCH v3 1/4] drm/xe/guc: Remove double blank line John.C.Harrison
2025-05-08 19:37   ` Michal Wajdeczko [this message]
2025-05-08  1:34 ` [PATCH v3 2/4] drm/xe/guc: Add missing H2G error code definitions John.C.Harrison
2025-05-08 19:50   ` Michal Wajdeczko
2025-05-12 19:30     ` John Harrison
2025-05-08  1:34 ` [PATCH v3 3/4] drm/xe/guc: Rename CONFIG_XE_LARGE_GUC_BUFFER John.C.Harrison
2025-05-08 19:52   ` Michal Wajdeczko
2025-05-08  1:34 ` [PATCH v3 4/4] drm/xe/guc: Track FAST_REQ H2Gs to report where errors came from John.C.Harrison
2025-05-08 20:11   ` Michal Wajdeczko
2025-05-12 19:52     ` John Harrison
2025-05-08  1:40 ` ✓ CI.Patch_applied: success for Track FAST_REQ H2Gs to report where errors came from (rev2) Patchwork
2025-05-08  1:40 ` ✗ CI.checkpatch: warning " Patchwork
2025-05-08  1:41 ` ✓ CI.KUnit: success " Patchwork
2025-05-08  1:50 ` ✓ CI.Build: " Patchwork
2025-05-08  1:52 ` ✓ CI.Hooks: " Patchwork
2025-05-08  1:53 ` ✓ CI.checksparse: " Patchwork
2025-05-08  2:15 ` ✓ Xe.CI.BAT: " Patchwork
2025-05-08 22:58 ` ✗ Xe.CI.Full: failure " Patchwork
2025-05-26 18:39 ` ✗ 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=e73487cb-eff4-449e-845b-5a55accd42e4@intel.com \
    --to=michal.wajdeczko@intel.com \
    --cc=Intel-Xe@Lists.FreeDesktop.Org \
    --cc=John.C.Harrison@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