Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Teres Alexis, Alan Previn" <alan.previn.teres.alexis@intel.com>
To: "Dong, Zhanjun" <zhanjun.dong@intel.com>,
	"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH v28 6/6] drm/xe/guc: Save manual engine capture into capture list
Date: Mon, 7 Oct 2024 14:17:14 +0000	[thread overview]
Message-ID: <81fc740223c48602e065661b5beba2e2619cdeda.camel@intel.com> (raw)
In-Reply-To: <20241004193428.3311145-7-zhanjun.dong@intel.com>

Reviewed-by: Alan Previn <alan.previn.teres.alexis@intel.com>

On Fri, 2024-10-04 at 12:34 -0700, Zhanjun Dong wrote:
> Save manual engine capture into capture list.
> This removes duplicate register definitions across manual-capture vs
> guc-err-capture.
> 
> Signed-off-by: Zhanjun Dong <zhanjun.dong@intel.com>


  reply	other threads:[~2024-10-07 14:17 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-04 19:34 [PATCH v28 0/6] drm/xe/guc: Add GuC based register capture for error capture Zhanjun Dong
2024-10-04 19:34 ` [PATCH v28 1/6] drm/xe/guc: Prepare GuC register list and update ADS size " Zhanjun Dong
2024-10-04 19:34 ` [PATCH v28 2/6] drm/xe/guc: Add XE_LP steered register lists Zhanjun Dong
2024-10-04 19:34 ` [PATCH v28 3/6] drm/xe/guc: Add capture size check in GuC log buffer Zhanjun Dong
2024-10-04 19:34 ` [PATCH v28 4/6] drm/xe/guc: Extract GuC error capture lists Zhanjun Dong
2024-10-04 19:34 ` [PATCH v28 5/6] drm/xe/guc: Plumb GuC-capture into dev coredump Zhanjun Dong
2024-10-22 11:28   ` Nirmoy Das
2024-10-04 19:34 ` [PATCH v28 6/6] drm/xe/guc: Save manual engine capture into capture list Zhanjun Dong
2024-10-07 14:17   ` Teres Alexis, Alan Previn [this message]
2024-10-09 19:22   ` [v28,6/6] " Kees Bakker
2024-10-07 13:15 ` ✓ CI.Patch_applied: success for drm/xe/guc: Add GuC based register capture for error capture (rev28) Patchwork
2024-10-07 13:16 ` ✗ CI.checkpatch: warning " Patchwork
2024-10-07 13:17 ` ✓ CI.KUnit: success " Patchwork
2024-10-07 13:28 ` ✓ CI.Build: " Patchwork
2024-10-07 13:30 ` ✓ CI.Hooks: " Patchwork
2024-10-07 13:32 ` ✓ CI.checksparse: " Patchwork
2024-10-07 13:52 ` ✓ CI.BAT: " Patchwork
2024-10-08  6:26 ` ✗ CI.FULL: failure " Patchwork
2024-10-08 13:11   ` Dong, Zhanjun
2024-10-08 16:48     ` Matt Roper

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=81fc740223c48602e065661b5beba2e2619cdeda.camel@intel.com \
    --to=alan.previn.teres.alexis@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=zhanjun.dong@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