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 (rev3)
Date: Tue, 11 Jan 2022 14:22:50 -0000 [thread overview]
Message-ID: <164191097030.24978.4700712540280966568@emeril.freedesktop.org> (raw)
In-Reply-To: <20220111093018.610582-1-alan.previn.teres.alexis@intel.com>
== Series Details ==
Series: Add GuC Error Capture Support (rev3)
URL : https://patchwork.freedesktop.org/series/97187/
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-01-11 14:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 9:30 [RFC v3 0/7] Add GuC Error Capture Support Alan Previn
2022-01-11 9:30 ` [Intel-gfx] " Alan Previn
2022-01-11 9:30 ` [Intel-gfx] [RFC v3 1/7] drm/i915/guc: Add basic support for error capture lists Alan Previn
2022-01-11 9:30 ` [Intel-gfx] [RFC v3 2/7] drm/i915/guc: Update GuC ADS size " Alan Previn
2022-01-11 9:30 ` [Intel-gfx] [RFC v3 3/7] drm/i915/guc: Populate XE_LP register lists for GuC error state capture Alan Previn
2022-01-11 9:30 ` [Intel-gfx] [RFC v3 4/7] drm/i915/guc: Add GuC's error state capture output structures Alan Previn
2022-01-11 9:30 ` [Intel-gfx] [RFC v3 5/7] drm/i915/guc: Update GuC's log-buffer-state access for error capture Alan Previn
2022-01-11 9:30 ` [Intel-gfx] [RFC v3 6/7] drm/i915/guc: Copy new GuC error capture logs upon G2H notification Alan Previn
2022-01-11 9:30 ` [Intel-gfx] [RFC v3 7/7] drm/i915/guc: Print the GuC error capture output register list Alan Previn
2022-01-11 21:54 ` Teres Alexis, Alan Previn
2022-01-11 14:21 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Add GuC Error Capture Support (rev3) Patchwork
2022-01-11 14:22 ` Patchwork [this message]
2022-01-11 14:38 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " 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=164191097030.24978.4700712540280966568@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.