From: Patchwork <patchwork@emeril.freedesktop.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.SPARSE: warning for series starting with [01/13] drm/i915: Don't set queue_priority_hint if we don't kick the submission
Date: Fri, 18 Oct 2019 22:36:23 -0000 [thread overview]
Message-ID: <20191018223623.27986.49335@emeril.freedesktop.org> (raw)
In-Reply-To: <20191018221450.26247-1-chris@chris-wilson.co.uk>
== Series Details ==
Series: series starting with [01/13] drm/i915: Don't set queue_priority_hint if we don't kick the submission
URL : https://patchwork.freedesktop.org/series/68243/
State : warning
== Summary ==
$ dim sparse origin/drm-tip
Sparse version: v0.6.0
Commit: drm/i915: Don't set queue_priority_hint if we don't kick the submission
Okay!
Commit: drm/i915/selftests: Add coverage of mocs registers
Okay!
Commit: drm/i915/selftests: Teach igt_flush_test and igt_live_test to take intel_gt
Okay!
Commit: drm/i915: Expose engine properties via sysfs
-
+drivers/gpu/drm/i915/gt/intel_engine_sysfs.c:52:10: error: bad integer constant expression
+drivers/gpu/drm/i915/gt/intel_engine_sysfs.c:53:10: error: bad integer constant expression
+drivers/gpu/drm/i915/gt/intel_engine_sysfs.c:57:10: error: bad integer constant expression
+drivers/gpu/drm/i915/gt/intel_engine_sysfs.c:73:20: error: undefined identifier 'engine'
+drivers/gpu/drm/i915/gt/intel_engine_sysfs.c:96:9: error: cannot size expression
+drivers/gpu/drm/i915/gt/intel_engine_sysfs.c:99:9: error: cannot size expression
+drivers/gpu/drm/i915/gt/intel_engine_sysfs.c:99:9: error: cannot size expression
+drivers/gpu/drm/i915/gt/intel_engine_sysfs.c:99:9: error: cannot size expression
Commit: drm/i915: Expose timeslice duration to sysfs
Okay!
Commit: drm/i915/execlists: Force preemption
Okay!
Commit: drm/i915/gt: Introduce barrier pulses along engines
Okay!
Commit: drm/i915/execlists: Cancel banned contexts on schedule-out
Okay!
Commit: drm/i915/gem: Cancel contexts when hangchecking is disabled
Okay!
Commit: drm/i915: Replace hangcheck by heartbeats
Okay!
Commit: drm/i915/gem: Make context persistence optional
Okay!
Commit: drm/i915/gem: Distinguish each object type
Okay!
Commit: drm/i915: Flush idle barriers when waiting
Okay!
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-10-18 22:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-18 22:14 [PATCH 01/13] drm/i915: Don't set queue_priority_hint if we don't kick the submission Chris Wilson
2019-10-18 22:14 ` [PATCH 02/13] drm/i915/selftests: Add coverage of mocs registers Chris Wilson
2019-10-18 23:24 ` Kumar Valsan, Prathap
2019-10-18 23:20 ` Chris Wilson
2019-10-21 13:52 ` Kumar Valsan, Prathap
2019-10-21 20:31 ` Chris Wilson
2019-10-18 22:14 ` [PATCH 03/13] drm/i915/selftests: Teach igt_flush_test and igt_live_test to take intel_gt Chris Wilson
2019-10-18 22:14 ` [PATCH 04/13] drm/i915: Expose engine properties via sysfs Chris Wilson
2019-10-18 22:14 ` [PATCH 05/13] drm/i915: Expose timeslice duration to sysfs Chris Wilson
2019-10-18 22:14 ` [PATCH 06/13] drm/i915/execlists: Force preemption Chris Wilson
2019-10-18 22:14 ` [PATCH 07/13] drm/i915/gt: Introduce barrier pulses along engines Chris Wilson
2019-10-18 22:14 ` [PATCH 08/13] drm/i915/execlists: Cancel banned contexts on schedule-out Chris Wilson
2019-10-18 22:14 ` [PATCH 09/13] drm/i915/gem: Cancel contexts when hangchecking is disabled Chris Wilson
2019-10-18 22:14 ` [PATCH 10/13] drm/i915: Replace hangcheck by heartbeats Chris Wilson
2019-10-18 22:14 ` [PATCH 11/13] drm/i915/gem: Make context persistence optional Chris Wilson
2019-10-18 22:14 ` [PATCH 12/13] drm/i915/gem: Distinguish each object type Chris Wilson
2019-10-18 22:14 ` [PATCH 13/13] drm/i915: Flush idle barriers when waiting Chris Wilson
2019-10-18 22:29 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [01/13] drm/i915: Don't set queue_priority_hint if we don't kick the submission Patchwork
2019-10-18 22:36 ` Patchwork [this message]
2019-10-18 22:57 ` ✗ 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=20191018223623.27986.49335@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=chris@chris-wilson.co.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox