From: Patchwork <patchwork@emeril.freedesktop.org>
To: Ville Syrjala <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.SPARSE: warning for drm/i915: GTT remapping for display
Date: Fri, 11 Jan 2019 20:02:32 -0000 [thread overview]
Message-ID: <20190111200232.4428.46009@emeril.freedesktop.org> (raw)
In-Reply-To: <20190111194704.23900-1-ville.syrjala@linux.intel.com>
== Series Details ==
Series: drm/i915: GTT remapping for display
URL : https://patchwork.freedesktop.org/series/55095/
State : warning
== Summary ==
$ dim sparse origin/drm-tip
Sparse version: v0.5.2
Commit: drm/i915: Add a new "remapped" gtt_view
+drivers/gpu/drm/i915/i915_gem_gtt.c:3630:34: warning: expression using sizeof(void)
+drivers/gpu/drm/i915/i915_gem_gtt.c:3630:34: warning: expression using sizeof(void)
-drivers/gpu/drm/i915/selftests/../i915_drv.h:3546:16: warning: expression using sizeof(void)
+drivers/gpu/drm/i915/selftests/../i915_drv.h:3550:16: warning: expression using sizeof(void)
Commit: drm/i915/selftests: Add mock selftest for remapped vmas
Okay!
Commit: drm/i915/selftests: Add live vma selftest
Okay!
Commit: drm/i915: Overcome display engine stride limits via GTT remapping
Okay!
Commit: drm/i915: Bump gen4+ fb stride limit to 256KiB
Okay!
Commit: drm/i915: Bump gen7+ fb size limits to 16kx16k
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-01-11 20:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-11 19:46 [PATCH v2 0/6] drm/i915: GTT remapping for display Ville Syrjala
2019-01-11 19:46 ` [PATCH v2 1/6] drm/i915: Add a new "remapped" gtt_view Ville Syrjala
2019-01-14 9:55 ` Tvrtko Ursulin
2019-01-15 10:58 ` Chris Wilson
2019-01-15 11:11 ` Tvrtko Ursulin
2019-01-15 13:43 ` Ville Syrjälä
2019-01-15 14:18 ` Chris Wilson
2019-01-24 23:24 ` Chris Wilson
2019-01-11 19:47 ` [PATCH v2 2/6] drm/i915/selftests: Add mock selftest for remapped vmas Ville Syrjala
2019-01-11 19:47 ` [PATCH v2 3/6] drm/i915/selftests: Add live vma selftest Ville Syrjala
2019-01-11 19:47 ` [PATCH v2 4/6] drm/i915: Overcome display engine stride limits via GTT remapping Ville Syrjala
2019-01-11 19:47 ` [PATCH v2 5/6] drm/i915: Bump gen4+ fb stride limit to 256KiB Ville Syrjala
2019-01-11 19:47 ` [PATCH v2 6/6] drm/i915: Bump gen7+ fb size limits to 16kx16k Ville Syrjala
2019-01-11 20:00 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: GTT remapping for display Patchwork
2019-01-11 20:02 ` Patchwork [this message]
2019-01-11 20:18 ` ✓ Fi.CI.BAT: success " Patchwork
2019-01-12 2:57 ` ✗ Fi.CI.IGT: failure " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2019-05-09 12:21 [PATCH v4 0/8] " Ville Syrjala
2019-05-09 14:58 ` ✗ Fi.CI.SPARSE: warning for " Patchwork
2019-01-18 15:27 [PATCH v3 0/8] " Ville Syrjala
2019-01-18 15:44 ` ✗ Fi.CI.SPARSE: warning for " Patchwork
2018-09-25 19:37 [PATCH v3 0/8] " Ville Syrjala
2018-09-25 20:08 ` ✗ Fi.CI.SPARSE: warning for " Patchwork
2018-07-19 18:21 [PATCH 00/18] " Ville Syrjala
2018-07-19 19:00 ` ✗ 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=20190111200232.4428.46009@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ville.syrjala@linux.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 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).