From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Matthew Brost" <matthew.brost@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.SPARSE: warning for Fix stealing guc_ids + test
Date: Sat, 11 Dec 2021 02:30:05 -0000 [thread overview]
Message-ID: <163918980575.10521.1381697933130898774@emeril.freedesktop.org> (raw)
In-Reply-To: <20211211005612.8575-1-matthew.brost@intel.com>
== Series Details ==
Series: Fix stealing guc_ids + test
URL : https://patchwork.freedesktop.org/series/97896/
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:[~2021-12-11 2:30 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-11 0:56 [PATCH 0/7] Fix stealing guc_ids + test Matthew Brost
2021-12-11 0:56 ` [Intel-gfx] " Matthew Brost
2021-12-11 0:56 ` [PATCH 1/7] drm/i915/guc: Use correct context lock when callig clr_context_registered Matthew Brost
2021-12-11 0:56 ` [Intel-gfx] " Matthew Brost
2021-12-11 0:56 ` [PATCH 2/7] drm/i915/guc: Only assign guc_id.id when stealing guc_id Matthew Brost
2021-12-11 0:56 ` [Intel-gfx] " Matthew Brost
2021-12-11 1:08 ` John Harrison
2021-12-11 1:08 ` [Intel-gfx] " John Harrison
2021-12-11 0:56 ` [PATCH 3/7] drm/i915/guc: Remove racey GEM_BUG_ON Matthew Brost
2021-12-11 0:56 ` [Intel-gfx] " Matthew Brost
2021-12-11 0:56 ` [PATCH 4/7] drm/i915/guc: Don't hog IRQs when destroying contexts Matthew Brost
2021-12-11 0:56 ` [Intel-gfx] " Matthew Brost
2021-12-11 1:07 ` John Harrison
2021-12-11 1:07 ` [Intel-gfx] " John Harrison
2021-12-11 1:10 ` Matthew Brost
2021-12-11 1:10 ` [Intel-gfx] " Matthew Brost
2021-12-11 0:56 ` [PATCH 5/7] drm/i915/guc: Add extra debug on CT deadlock Matthew Brost
2021-12-11 0:56 ` [Intel-gfx] " Matthew Brost
2021-12-11 1:43 ` John Harrison
2021-12-11 1:43 ` [Intel-gfx] " John Harrison
2021-12-11 1:45 ` John Harrison
2021-12-11 3:24 ` Matthew Brost
2021-12-11 0:56 ` [PATCH 6/7] drm/i915/guc: Kick G2H tasklet if no credits Matthew Brost
2021-12-11 0:56 ` [Intel-gfx] " Matthew Brost
2021-12-11 0:56 ` [PATCH 7/7] drm/i915/guc: Selftest for stealing of guc ids Matthew Brost
2021-12-11 0:56 ` [Intel-gfx] " Matthew Brost
2021-12-11 1:33 ` John Harrison
2021-12-11 1:33 ` [Intel-gfx] " John Harrison
2021-12-11 3:31 ` Matthew Brost
2021-12-11 3:31 ` [Intel-gfx] " Matthew Brost
2021-12-11 3:32 ` Matthew Brost
2021-12-11 3:32 ` [Intel-gfx] " Matthew Brost
2021-12-11 2:28 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Fix stealing guc_ids + test Patchwork
2021-12-11 2:30 ` Patchwork [this message]
2021-12-11 2:58 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-12-12 1:32 ` [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=163918980575.10521.1381697933130898774@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.brost@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.