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/10] drm/i915/gem: Distinguish each object type
Date: Mon, 14 Oct 2019 23:15:07 -0000 [thread overview]
Message-ID: <20191014231507.23966.61453@emeril.freedesktop.org> (raw)
In-Reply-To: <20191014220534.1662-1-chris@chris-wilson.co.uk>
== Series Details ==
Series: series starting with [01/10] drm/i915/gem: Distinguish each object type
URL : https://patchwork.freedesktop.org/series/67993/
State : warning
== Summary ==
$ dim sparse origin/drm-tip
Sparse version: v0.6.0
Commit: drm/i915/gem: Distinguish each object type
Okay!
Commit: drm/i915/execlists: Clear semaphore immediately upon ELSP promotion
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/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 non-persistent contexts on close
Okay!
Commit: drm/i915: Replace hangcheck by heartbeats
Okay!
Commit: drm/i915/execlist: Trim immediate timeslice expiry
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-14 23:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-14 22:05 [PATCH 01/10] drm/i915/gem: Distinguish each object type Chris Wilson
2019-10-14 22:05 ` [PATCH 02/10] drm/i915/execlists: Clear semaphore immediately upon ELSP promotion Chris Wilson
2019-10-15 9:16 ` Tvrtko Ursulin
2019-10-15 9:26 ` Chris Wilson
2019-10-14 22:05 ` [PATCH 03/10] drm/i915: Expose engine properties via sysfs Chris Wilson
2019-10-15 9:14 ` Tvrtko Ursulin
2019-10-14 22:05 ` [PATCH 04/10] drm/i915/execlists: Force preemption Chris Wilson
2019-10-14 22:05 ` [PATCH 05/10] drm/i915/gt: Introduce barrier pulses along engines Chris Wilson
2019-10-14 22:05 ` [PATCH 06/10] drm/i915/execlists: Cancel banned contexts on schedule-out Chris Wilson
2019-10-14 22:05 ` [PATCH 07/10] drm/i915/gem: Cancel non-persistent contexts on close Chris Wilson
2019-10-15 12:15 ` Tvrtko Ursulin
2019-10-15 12:19 ` Chris Wilson
2019-10-15 12:49 ` Tvrtko Ursulin
2019-10-14 22:05 ` [PATCH 08/10] drm/i915: Replace hangcheck by heartbeats Chris Wilson
2019-10-14 22:05 ` [PATCH 09/10] drm/i915/execlist: Trim immediate timeslice expiry Chris Wilson
2019-10-15 12:43 ` Tvrtko Ursulin
2019-10-14 22:05 ` [PATCH 10/10] drm/i915: Flush idle barriers when waiting Chris Wilson
2019-10-14 23:09 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [01/10] drm/i915/gem: Distinguish each object type Patchwork
2019-10-14 23:15 ` Patchwork [this message]
2019-10-14 23:36 ` ✗ 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=20191014231507.23966.61453@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