From: Patchwork <patchwork@emeril.freedesktop.org>
To: john.c.harrison@intel.com
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.SPARSE: warning for Allow error capture without a request & fix locking issues (rev3)
Date: Thu, 26 Jan 2023 04:24:11 -0000 [thread overview]
Message-ID: <167470705105.542.2937498834557451231@emeril.freedesktop.org> (raw)
In-Reply-To: <20230126005420.160070-1-John.C.Harrison@Intel.com>
== Series Details ==
Series: Allow error capture without a request & fix locking issues (rev3)
URL : https://patchwork.freedesktop.org/series/113078/
State : warning
== Summary ==
Error: dim sparse failed
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
next prev parent reply other threads:[~2023-01-26 4:24 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-26 0:54 [PATCH v5 0/8] Allow error capture without a request & fix locking issues John.C.Harrison
2023-01-26 0:54 ` [Intel-gfx] " John.C.Harrison
2023-01-26 0:54 ` [PATCH v5 1/8] drm/i915/guc: Fix locking when searching for a hung request John.C.Harrison
2023-01-26 0:54 ` [Intel-gfx] " John.C.Harrison
2023-01-26 23:45 ` Ceraolo Spurio, Daniele
2023-01-26 23:45 ` [Intel-gfx] " Ceraolo Spurio, Daniele
2023-01-26 0:54 ` [PATCH v5 2/8] drm/i915: Fix request locking during error capture & debugfs dump John.C.Harrison
2023-01-26 0:54 ` [Intel-gfx] " John.C.Harrison
2023-01-26 9:06 ` Tvrtko Ursulin
2023-01-26 9:06 ` [Intel-gfx] " Tvrtko Ursulin
2023-01-26 0:54 ` [PATCH v5 3/8] drm/i915: Fix up locking around dumping requests lists John.C.Harrison
2023-01-26 0:54 ` [Intel-gfx] " John.C.Harrison
2023-01-26 0:54 ` [PATCH v5 4/8] drm/i915: Allow error capture without a request John.C.Harrison
2023-01-26 0:54 ` [Intel-gfx] " John.C.Harrison
2023-01-26 0:54 ` [PATCH v5 5/8] drm/i915: Allow error capture of a pending request John.C.Harrison
2023-01-26 0:54 ` [Intel-gfx] " John.C.Harrison
2023-01-26 0:54 ` [PATCH v5 6/8] drm/i915/guc: Look for a guilty context when an engine reset fails John.C.Harrison
2023-01-26 0:54 ` [Intel-gfx] " John.C.Harrison
2023-01-26 0:54 ` [PATCH v5 7/8] drm/i915/guc: Add a debug print on GuC triggered reset John.C.Harrison
2023-01-26 0:54 ` [Intel-gfx] " John.C.Harrison
2023-01-26 0:54 ` [PATCH v5 8/8] drm/i915/guc: Rename GuC register state capture node to be more obvious John.C.Harrison
2023-01-26 0:54 ` [Intel-gfx] " John.C.Harrison
2023-01-26 4:24 ` Patchwork [this message]
2023-01-26 4:50 ` [Intel-gfx] ✓ Fi.CI.BAT: success for Allow error capture without a request & fix locking issues (rev3) Patchwork
2023-01-26 15:21 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=167470705105.542.2937498834557451231@emeril.freedesktop.org \
--to=patchwork@emeril.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 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.