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 Update to GuC v70
Date: Wed, 13 Apr 2022 19:02:26 -0000 [thread overview]
Message-ID: <164987654683.28396.13087610919232485168@emeril.freedesktop.org> (raw)
In-Reply-To: <20220412225955.1802543-1-John.C.Harrison@Intel.com>
== Series Details ==
Series: Update to GuC v70
URL : https://patchwork.freedesktop.org/series/102626/
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-04-13 19:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 22:59 [PATCH 0/1] Update to GuC v70 John.C.Harrison
2022-04-12 22:59 ` [Intel-gfx] " John.C.Harrison
2022-04-12 22:59 ` [PATCH 1/1] drm/i915/guc: Update to GuC version 70.1.1 John.C.Harrison
2022-04-12 22:59 ` [Intel-gfx] " John.C.Harrison
2022-04-15 0:14 ` Matt Roper
2022-07-14 23:08 ` Dave Airlie
2022-07-14 23:08 ` Dave Airlie
2022-07-15 8:34 ` [Intel-gfx] [PATCH 1/1] drm/i915/guc: Update to GuC version 70.1.1 #forregzbot Thorsten Leemhuis
2022-07-15 9:04 ` Thorsten Leemhuis
2022-07-17 15:33 ` Thorsten Leemhuis
2022-07-21 12:51 ` Thorsten Leemhuis
2022-07-20 8:28 ` [Intel-gfx] [PATCH 1/1] drm/i915/guc: Update to GuC version 70.1.1 Jordan Justen
2022-07-20 8:28 ` Jordan Justen
2022-04-13 19:02 ` Patchwork [this message]
2022-04-13 19:25 ` [Intel-gfx] ✓ Fi.CI.BAT: success for Update to GuC v70 Patchwork
2022-04-13 21:35 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2022-04-08 18:03 [PATCH 0/3] " John.C.Harrison
2022-04-08 21: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=164987654683.28396.13087610919232485168@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.