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 Delay disabling GuC scheduling of an idle context
Date: Thu, 15 Sep 2022 03:22:16 -0000 [thread overview]
Message-ID: <166321213698.11974.838225871582320781@emeril.freedesktop.org> (raw)
In-Reply-To: <20220915021218.1412111-1-alan.previn.teres.alexis@intel.com>
== Series Details ==
Series: Delay disabling GuC scheduling of an idle context
URL : https://patchwork.freedesktop.org/series/108587/
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:[~2022-09-15 3:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-15 2:12 [Intel-gfx] [PATCH 0/1] Delay disabling GuC scheduling of an idle context Alan Previn
2022-09-15 2:12 ` [Intel-gfx] [PATCH 1/1] drm/i915/guc: Delay disabling guc_id scheduling for better hysteresis Alan Previn
2022-09-15 8:48 ` Tvrtko Ursulin
2022-09-16 7:53 ` Teres Alexis, Alan Previn
2022-09-16 8:58 ` Tvrtko Ursulin
2022-09-16 15:36 ` Ceraolo Spurio, Daniele
2022-09-20 6:22 ` Teres Alexis, Alan Previn
2022-09-20 14:33 ` Tvrtko Ursulin
2022-09-21 7:59 ` Teres Alexis, Alan Previn
2022-09-21 22:30 ` Teres Alexis, Alan Previn
2022-09-21 22:30 ` Teres Alexis, Alan Previn
2022-09-15 3:22 ` Patchwork [this message]
2022-09-15 3:41 ` [Intel-gfx] ✓ Fi.CI.BAT: success for Delay disabling GuC scheduling of an idle context Patchwork
2022-09-15 20:41 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-09-23 5:30 [Intel-gfx] [PATCH v3 0/1] " Alan Previn
2022-09-23 7:18 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for " Patchwork
2022-10-06 22:51 [Intel-gfx] [PATCH v5 0/1] " Alan Previn
2022-10-06 23:33 ` [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=166321213698.11974.838225871582320781@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.