From: Patchwork <patchwork@emeril.freedesktop.org>
To: Tomasz Lis <tomasz.lis@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.SPARSE: warning for drm/i915: Add Exec param to control data port coherency. (rev7)
Date: Tue, 09 Oct 2018 18:28:02 -0000 [thread overview]
Message-ID: <20181009182802.19903.28673@emeril.freedesktop.org> (raw)
In-Reply-To: <1521463055-5325-1-git-send-email-tomasz.lis@intel.com>
== Series Details ==
Series: drm/i915: Add Exec param to control data port coherency. (rev7)
URL : https://patchwork.freedesktop.org/series/40181/
State : warning
== Summary ==
$ dim sparse origin/drm-tip
Sparse version: v0.5.2
Commit: drm/i915: Add IOCTL Param to control data port coherency.
-drivers/gpu/drm/i915/selftests/../i915_drv.h:3727:16: warning: expression using sizeof(void)
+drivers/gpu/drm/i915/selftests/../i915_drv.h:3728:16: warning: expression using sizeof(void)
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-10-09 18:28 UTC|newest]
Thread overview: 81+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-19 12:37 [RFC v1] Data port coherency control for UMDs Tomasz Lis
2018-03-19 12:37 ` [RFC v1] drm/i915: Add Exec param to control data port coherency Tomasz Lis
2018-03-19 12:43 ` Chris Wilson
2018-03-19 14:14 ` Lis, Tomasz
2018-03-19 14:26 ` Chris Wilson
2018-03-20 17:23 ` Lis, Tomasz
2018-05-04 9:24 ` Joonas Lahtinen
2018-03-20 18:43 ` Oscar Mateo
2018-03-21 10:16 ` Chris Wilson
2018-03-21 19:42 ` Oscar Mateo
2018-03-27 17:41 ` Lis, Tomasz
2018-03-30 17:29 ` [PATCH " Tomasz Lis
2018-03-31 19:07 ` kbuild test robot
2018-04-11 15:46 ` [PATCH v2] " Tomasz Lis
2018-06-20 15:03 ` [PATCH v1] Second implementation of Data Port Coherency Tomasz Lis
2018-06-20 15:03 ` [PATCH v1] drm/i915: Add IOCTL Param to control data port coherency Tomasz Lis
2018-06-21 6:39 ` Joonas Lahtinen
2018-06-21 13:47 ` Lis, Tomasz
2018-07-18 13:03 ` Joonas Lahtinen
2018-06-21 7:05 ` Chris Wilson
2018-06-21 13:47 ` Lis, Tomasz
2018-06-21 7:31 ` Dunajski, Bartosz
2018-06-21 8:48 ` Joonas Lahtinen
2018-06-22 16:40 ` Dunajski, Bartosz
2018-07-18 13:12 ` Joonas Lahtinen
2018-07-18 13:27 ` Dunajski, Bartosz
2018-07-09 13:20 ` [PATCH v4] " Tomasz Lis
2018-07-09 13:48 ` Lionel Landwerlin
2018-07-09 14:03 ` Lis, Tomasz
2018-07-09 14:24 ` Lionel Landwerlin
2018-07-09 15:21 ` Lis, Tomasz
2018-07-09 16:28 ` Tvrtko Ursulin
2018-07-09 16:37 ` Chris Wilson
2018-07-10 17:32 ` Lis, Tomasz
2018-07-11 9:28 ` Tvrtko Ursulin
2018-07-10 18:03 ` Lis, Tomasz
2018-07-11 11:20 ` Lis, Tomasz
2018-07-12 15:10 ` [PATCH v5] " Tomasz Lis
2018-07-13 10:40 ` Tvrtko Ursulin
2018-07-13 17:44 ` Lis, Tomasz
2018-10-09 18:06 ` [PATCH v6] " Tomasz Lis
2018-10-10 7:29 ` Tvrtko Ursulin
2018-10-12 15:02 ` [PATCH v8] " Tomasz Lis
2018-10-15 12:52 ` Tvrtko Ursulin
2018-10-16 13:59 ` Joonas Lahtinen
2018-03-19 13:53 ` [RFC v1] Data port coherency control for UMDs Joonas Lahtinen
2018-03-19 16:09 ` Lis, Tomasz
2018-03-20 15:15 ` Dunajski, Bartosz
2018-03-21 10:02 ` Joonas Lahtinen
2018-03-26 9:46 ` Dunajski, Bartosz
2018-03-29 7:42 ` Joonas Lahtinen
2018-03-30 9:00 ` Dunajski, Bartosz
2018-04-04 9:18 ` Joonas Lahtinen
2018-04-11 9:15 ` Dunajski, Bartosz
2018-03-19 14:18 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Add Exec param to control data port coherency Patchwork
2018-03-19 14:34 ` ✓ Fi.CI.BAT: success " Patchwork
2018-03-19 16:48 ` ✗ Fi.CI.IGT: failure " Patchwork
2018-03-30 18:14 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Add Exec param to control data port coherency. (rev2) Patchwork
2018-03-30 18:30 ` ✓ Fi.CI.BAT: success " Patchwork
2018-03-30 19:59 ` ✗ Fi.CI.IGT: failure " Patchwork
2018-04-11 16:12 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Add Exec param to control data port coherency. (rev3) Patchwork
2018-04-11 16:29 ` ✓ Fi.CI.BAT: success " Patchwork
2018-04-11 20:02 ` ✗ Fi.CI.IGT: failure " Patchwork
2018-06-20 15:45 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Add Exec param to control data port coherency. (rev4) Patchwork
2018-06-20 16:00 ` ✓ Fi.CI.BAT: success " Patchwork
2018-06-20 21:01 ` ✗ Fi.CI.IGT: failure " Patchwork
2018-07-09 13:57 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Add Exec param to control data port coherency. (rev5) Patchwork
2018-07-09 13:58 ` ✗ Fi.CI.SPARSE: " Patchwork
2018-07-09 14:14 ` ✓ Fi.CI.BAT: success " Patchwork
2018-07-09 20:04 ` ✗ Fi.CI.IGT: failure " Patchwork
2018-07-12 15:18 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Add Exec param to control data port coherency. (rev6) Patchwork
2018-07-12 15:19 ` ✗ Fi.CI.SPARSE: " Patchwork
2018-07-12 15:34 ` ✓ Fi.CI.BAT: success " Patchwork
2018-10-09 18:27 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Add Exec param to control data port coherency. (rev7) Patchwork
2018-10-09 18:28 ` Patchwork [this message]
2018-10-09 18:52 ` ✓ Fi.CI.BAT: success " Patchwork
2018-10-09 21:44 ` ✗ Fi.CI.IGT: failure " Patchwork
2018-10-12 15:14 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Add Exec param to control data port coherency. (rev8) Patchwork
2018-10-12 15:15 ` ✗ Fi.CI.SPARSE: " Patchwork
2018-10-12 15:34 ` ✓ Fi.CI.BAT: success " Patchwork
2018-10-12 18:27 ` ✗ Fi.CI.IGT: 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=20181009182802.19903.28673@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=tomasz.lis@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).