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 [1/6] drm/i915: Refactor export_fence() after i915_vma_move_to_active() (rev3)
Date: Wed, 04 Jul 2018 09:37:10 -0000 [thread overview]
Message-ID: <20180704093710.6643.8596@emeril.freedesktop.org> (raw)
In-Reply-To: <20180629225419.5832-1-chris@chris-wilson.co.uk>
== Series Details ==
Series: series starting with [1/6] drm/i915: Refactor export_fence() after i915_vma_move_to_active() (rev3)
URL : https://patchwork.freedesktop.org/series/45689/
State : warning
== Summary ==
$ dim sparse origin/drm-tip
Commit: drm/i915: Refactor export_fence() after i915_vma_move_to_active()
Okay!
Commit: drm/i915: Export i915_request_skip()
Okay!
Commit: drm/i915: Start returning an error from i915_vma_move_to_active()
Okay!
Commit: drm/i915: Move i915_vma_move_to_active() to i915_vma.c
-drivers/gpu/drm/i915/selftests/../i915_drv.h:3664:16: warning: expression using sizeof(void)
+drivers/gpu/drm/i915/selftests/../i915_drv.h:3661:16: warning: expression using sizeof(void)
Commit: drm/i915: Track vma activity per fence.context, not per engine
Okay!
Commit: drm/i915: Track the last-active inside the i915_vma
Okay!
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-07-04 9:37 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-29 22:54 [PATCH 1/6] drm/i915: Refactor export_fence() after i915_vma_move_to_active() Chris Wilson
2018-06-29 22:54 ` [PATCH 2/6] drm/i915: Export i915_request_skip() Chris Wilson
2018-07-02 11:37 ` Tvrtko Ursulin
2018-06-29 22:54 ` [PATCH 3/6] drm/i915: Start returning an error from i915_vma_move_to_active() Chris Wilson
2018-07-02 11:41 ` Tvrtko Ursulin
2018-06-29 22:54 ` [PATCH 4/6] drm/i915: Move i915_vma_move_to_active() to i915_vma.c Chris Wilson
2018-07-02 11:41 ` Tvrtko Ursulin
2018-06-29 22:54 ` [PATCH 5/6] drm/i915: Track vma activity per fence.context, not per engine Chris Wilson
2018-07-03 17:28 ` Tvrtko Ursulin
2018-07-03 20:29 ` Chris Wilson
2018-07-04 9:43 ` Tvrtko Ursulin
2018-07-04 9:53 ` Chris Wilson
2018-07-04 9:13 ` [PATCH v3] " Chris Wilson
2018-07-04 11:19 ` Tvrtko Ursulin
2018-06-29 22:54 ` [PATCH 6/6] drm/i915: Track the last-active inside the i915_vma Chris Wilson
2018-07-03 17:40 ` Tvrtko Ursulin
2018-07-04 8:34 ` [PATCH v2] " Chris Wilson
2018-07-04 9:39 ` Tvrtko Ursulin
2018-07-04 11:34 ` Tvrtko Ursulin
2018-07-04 11:47 ` Chris Wilson
2018-07-04 12:30 ` Tvrtko Ursulin
2018-07-05 11:38 ` Tvrtko Ursulin
2018-07-05 12:02 ` Chris Wilson
2018-07-05 12:29 ` Tvrtko Ursulin
2018-07-05 12:48 ` Chris Wilson
2018-06-29 23:04 ` ✗ Fi.CI.SPARSE: warning for series starting with [1/6] drm/i915: Refactor export_fence() after i915_vma_move_to_active() Patchwork
2018-06-29 23:19 ` ✓ Fi.CI.BAT: success " Patchwork
2018-06-30 3:03 ` ✓ Fi.CI.IGT: " Patchwork
2018-07-02 11:34 ` [PATCH 1/6] " Tvrtko Ursulin
2018-07-02 11:44 ` Chris Wilson
2018-07-02 12:29 ` Tvrtko Ursulin
2018-07-04 8:52 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/6] drm/i915: Refactor export_fence() after i915_vma_move_to_active() (rev2) Patchwork
2018-07-04 8:55 ` ✗ Fi.CI.SPARSE: " Patchwork
2018-07-04 9:07 ` ✓ Fi.CI.BAT: success " Patchwork
2018-07-04 9:34 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/6] drm/i915: Refactor export_fence() after i915_vma_move_to_active() (rev3) Patchwork
2018-07-04 9:37 ` Patchwork [this message]
2018-07-04 9:49 ` ✓ Fi.CI.BAT: success " Patchwork
2018-07-04 10:43 ` ✓ 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=20180704093710.6643.8596@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;
as well as URLs for NNTP newsgroup(s).