From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Alan Previn" <alan.previn.teres.alexis@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.SPARSE: warning for Add GuC Error Capture Support
Date: Mon, 14 Mar 2022 20:13:06 -0000 [thread overview]
Message-ID: <164728878636.20566.10447390804493772777@emeril.freedesktop.org> (raw)
In-Reply-To: <20220314170954.1537154-1-alan.previn.teres.alexis@intel.com>
== Series Details ==
Series: Add GuC Error Capture Support
URL : https://patchwork.freedesktop.org/series/101348/
State : warning
== Summary ==
$ dim sparse --fast origin/drm-tip
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
next prev parent reply other threads:[~2022-03-14 20:13 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-14 17:09 [PATCH v9 00/13] Add GuC Error Capture Support Alan Previn
2022-03-14 17:09 ` [Intel-gfx] " Alan Previn
2022-03-14 17:09 ` [Intel-gfx] [PATCH v9 01/13] drm/i915/guc: Update GuC ADS size for error capture lists Alan Previn
2022-03-15 15:17 ` Matthew Brost
2022-03-15 16:06 ` Teres Alexis, Alan Previn
2022-03-14 17:09 ` [Intel-gfx] [PATCH v9 02/13] drm/i915/guc: Add XE_LP static registers for GuC error capture Alan Previn
2022-03-14 17:09 ` [Intel-gfx] [PATCH v9 03/13] drm/i915/guc: Add XE_LP steered register lists support Alan Previn
2022-03-14 17:09 ` [Intel-gfx] [PATCH v9 04/13] drm/i915/guc: Add DG2 registers for GuC error state capture Alan Previn
2022-03-14 17:09 ` [Intel-gfx] [PATCH v9 05/13] drm/i915/guc: Add Gen9 " Alan Previn
2022-03-14 17:09 ` [Intel-gfx] [PATCH v9 06/13] drm/i915/guc: Add GuC's error state capture output structures Alan Previn
2022-03-14 17:09 ` [Intel-gfx] [PATCH v9 07/13] drm/i915/guc: Update GuC-log relay function names Alan Previn
2022-03-14 17:09 ` [Intel-gfx] [PATCH v9 08/13] drm/i915/guc: Add capture region into intel_guc_log Alan Previn
2022-03-14 17:09 ` [Intel-gfx] [PATCH v9 09/13] drm/i915/guc: Check sizing of guc_capture output Alan Previn
2022-03-14 17:09 ` [Intel-gfx] [PATCH v9 10/13] drm/i915/guc: Extract GuC error capture lists on G2H notification Alan Previn
2022-03-14 17:09 ` [Intel-gfx] [PATCH v9 11/13] drm/i915/guc: Pre-allocate output nodes for extraction Alan Previn
2022-03-14 17:09 ` [Intel-gfx] [PATCH v9 12/13] drm/i915/guc: Plumb GuC-capture into gpu_coredump Alan Previn
2022-03-14 17:09 ` [Intel-gfx] [PATCH v9 13/13] drm/i915/guc: Print the GuC error capture output register list Alan Previn
2022-03-14 23:42 ` kernel test robot
2022-03-15 2:26 ` kernel test robot
2022-03-16 1:04 ` Teres Alexis, Alan Previn
2022-03-16 1:04 ` Teres Alexis, Alan Previn
2022-03-14 20:11 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Add GuC Error Capture Support Patchwork
2022-03-14 20:13 ` Patchwork [this message]
2022-03-14 20:46 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2022-03-15 18:24 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Add GuC Error Capture Support (rev2) Patchwork
2022-03-16 1:24 ` Teres Alexis, Alan Previn
2022-03-15 18:25 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-03-15 18:58 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-03-15 22:50 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2022-03-21 16:45 [PATCH v13 00/13] Add GuC Error Capture Support Alan Previn
2022-03-21 21:53 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for " Patchwork
2022-03-18 6:42 [PATCH v12 00/13] " Alan Previn
2022-03-18 7:03 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for " Patchwork
2022-03-17 18:56 [PATCH v11 00/13] " Alan Previn
2022-03-17 21:43 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for " Patchwork
2022-03-16 1:50 [PATCH v10 00/13] " Alan Previn
2022-03-16 2:03 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for " Patchwork
2021-11-22 23:03 [RFC 0/7] " Alan Previn
2021-11-22 23:45 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for " 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=164728878636.20566.10447390804493772777@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=alan.previn.teres.alexis@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.