Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: John.C.Harrison@Intel.com, Intel-GFX@Lists.FreeDesktop.Org
Cc: DRI-Devel@Lists.FreeDesktop.Org
Subject: Re: [Intel-gfx] [PATCH v2 0/6] More drm_dbg to guc_dbg changes
Date: Tue, 7 Feb 2023 23:34:15 +0100	[thread overview]
Message-ID: <bf48f3bb-6cf1-49fb-d3b9-f0738c404516@intel.com> (raw)
In-Reply-To: <20230207050717.1833718-1-John.C.Harrison@Intel.com>



On 07.02.2023 06:07, John.C.Harrison@Intel.com wrote:
> From: John Harrison <John.C.Harrison@Intel.com>
> 
> Update more print messages to the new scheme.
> 
> v2: Also change all errors to %pe rather than %d (MichalW).
> Few other tweaks.
> 
> Signed-off-by: John Harrison <John.C.Harrison@Intel.com>

LGTM, series is

Reviewed-by: Michal Wajdeczko <michal.wajdeczko@intel.com>

> 
> 
> John Harrison (6):
>   drm/i915/guc: More debug print updates - UC firmware
>   drm/i915/guc: More debug print updates - GSC firmware
>   drm/i915/guc: More debug print updates - GuC reg capture
>   drm/i915/guc: More debug print updates - GuC selftests
>   drm/i915/guc: More debug print updates - GuC SLPC
>   drm/i915/guc: More debug print updates - GuC logging
> 
>  drivers/gpu/drm/i915/gt/intel_gt_print.h      |   3 +
>  drivers/gpu/drm/i915/gt/uc/intel_gsc_fw.c     |   9 +-
>  drivers/gpu/drm/i915/gt/uc/intel_gsc_uc.c     |   7 +-
>  .../gpu/drm/i915/gt/uc/intel_guc_capture.c    |  51 ++++----
>  drivers/gpu/drm/i915/gt/uc/intel_guc_log.c    |   3 +-
>  drivers/gpu/drm/i915/gt/uc/intel_guc_print.h  |   3 +
>  drivers/gpu/drm/i915/gt/uc/intel_guc_rc.c     |   8 +-
>  drivers/gpu/drm/i915/gt/uc/intel_guc_slpc.c   |  61 ++++-----
>  drivers/gpu/drm/i915/gt/uc/intel_uc.c         |  42 +++----
>  drivers/gpu/drm/i915/gt/uc/intel_uc_fw.c      | 116 +++++++++---------
>  drivers/gpu/drm/i915/gt/uc/selftest_guc.c     |  42 ++++---
>  .../drm/i915/gt/uc/selftest_guc_hangcheck.c   |  23 ++--
>  .../drm/i915/gt/uc/selftest_guc_multi_lrc.c   |  11 +-
>  13 files changed, 174 insertions(+), 205 deletions(-)
> 

      parent reply	other threads:[~2023-02-07 22:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-07  5:07 [Intel-gfx] [PATCH v2 0/6] More drm_dbg to guc_dbg changes John.C.Harrison
2023-02-07  5:07 ` [Intel-gfx] [PATCH v2 1/6] drm/i915/guc: More debug print updates - UC firmware John.C.Harrison
2023-02-07  5:07 ` [Intel-gfx] [PATCH v2 2/6] drm/i915/guc: More debug print updates - GSC firmware John.C.Harrison
2023-02-07  5:07 ` [Intel-gfx] [PATCH v2 3/6] drm/i915/guc: More debug print updates - GuC reg capture John.C.Harrison
2023-02-07  5:07 ` [Intel-gfx] [PATCH v2 4/6] drm/i915/guc: More debug print updates - GuC selftests John.C.Harrison
2023-02-07  5:07 ` [Intel-gfx] [PATCH v2 5/6] drm/i915/guc: More debug print updates - GuC SLPC John.C.Harrison
2023-02-07  5:07 ` [Intel-gfx] [PATCH v2 6/6] drm/i915/guc: More debug print updates - GuC logging John.C.Harrison
2023-02-07  5:32 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for More drm_dbg to guc_dbg changes (rev2) Patchwork
2023-02-07  5:58 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-02-07 11:03 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2023-02-07 22:34 ` Michal Wajdeczko [this message]

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=bf48f3bb-6cf1-49fb-d3b9-f0738c404516@intel.com \
    --to=michal.wajdeczko@intel.com \
    --cc=DRI-Devel@Lists.FreeDesktop.Org \
    --cc=Intel-GFX@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