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/7] drm/i915: Allocate a common scratch page
Date: Tue, 04 Dec 2018 14:31:12 -0000 [thread overview]
Message-ID: <20181204143112.4007.71484@emeril.freedesktop.org> (raw)
In-Reply-To: <20181204141522.13640-1-chris@chris-wilson.co.uk>
== Series Details ==
Series: series starting with [1/7] drm/i915: Allocate a common scratch page
URL : https://patchwork.freedesktop.org/series/53477/
State : warning
== Summary ==
$ dim sparse origin/drm-tip
Sparse version: v0.5.2
Commit: drm/i915: Allocate a common scratch page
-drivers/gpu/drm/i915/selftests/../i915_drv.h:3560:16: warning: expression using sizeof(void)
+drivers/gpu/drm/i915/selftests/../i915_drv.h:3562:16: warning: expression using sizeof(void)
Commit: drm/i915: Flush GPU relocs harder for gen3
Okay!
Commit: drm/i915/selftests: Reorder request allocation vs vma pinning
Okay!
Commit: drm/i915: Pipeline PDP updates for Braswell
Okay!
Commit: drm/i915: Return immediately if trylock fails for direct-reclaim
Okay!
Commit: drm/i915/userptr: Avoid struct_mutex recursion for mmu_invalidate_range_start
Okay!
Commit: drm/i915/userptr: Probe vma range before gup
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-12-04 14:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-04 14:15 [PATCH 1/7] drm/i915: Allocate a common scratch page Chris Wilson
2018-12-04 14:15 ` [PATCH 2/7] drm/i915: Flush GPU relocs harder for gen3 Chris Wilson
2018-12-04 14:15 ` [PATCH 3/7] drm/i915/selftests: Reorder request allocation vs vma pinning Chris Wilson
2018-12-04 14:15 ` [PATCH 4/7] drm/i915: Pipeline PDP updates for Braswell Chris Wilson
2018-12-04 14:15 ` [PATCH 5/7] drm/i915: Return immediately if trylock fails for direct-reclaim Chris Wilson
2018-12-06 15:18 ` Tvrtko Ursulin
2018-12-06 21:30 ` Chris Wilson
2018-12-07 8:38 ` Chris Wilson
2018-12-10 11:29 ` Tvrtko Ursulin
2018-12-04 14:15 ` [PATCH 6/7] drm/i915/userptr: Avoid struct_mutex recursion for mmu_invalidate_range_start Chris Wilson
2018-12-10 12:00 ` Tvrtko Ursulin
2018-12-04 14:15 ` [PATCH 7/7] drm/i915/userptr: Probe vma range before gup Chris Wilson
2018-12-04 14:28 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/7] drm/i915: Allocate a common scratch page Patchwork
2018-12-04 14:31 ` Patchwork [this message]
2018-12-04 14:48 ` ✓ Fi.CI.BAT: success " Patchwork
2018-12-04 15:53 ` Chris Wilson
2018-12-04 15:07 ` [PATCH 1/7] " Mika Kuoppala
2018-12-04 16:01 ` Chris Wilson
2018-12-04 22:58 ` ✓ Fi.CI.IGT: success for series starting with [1/7] " 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=20181204143112.4007.71484@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