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/2] drm/i915/overlay: Allocate physical registers from stolen
Date: Thu, 06 Sep 2018 19:29:48 -0000 [thread overview]
Message-ID: <20180906192948.5277.80772@emeril.freedesktop.org> (raw)
In-Reply-To: <20180906190144.1272-1-chris@chris-wilson.co.uk>
== Series Details ==
Series: series starting with [1/2] drm/i915/overlay: Allocate physical registers from stolen
URL : https://patchwork.freedesktop.org/series/49295/
State : warning
== Summary ==
$ dim sparse origin/drm-tip
Commit: drm/i915/overlay: Allocate physical registers from stolen
Okay!
Commit: drm/i915/overlay: Use the ioctl parameters directly
-O:drivers/gpu/drm/i915/intel_overlay.c:832:29: warning: expression using sizeof(void)
-O:drivers/gpu/drm/i915/intel_overlay.c:832:29: warning: expression using sizeof(void)
+drivers/gpu/drm/i915/intel_overlay.c:819:29: warning: expression using sizeof(void)
+drivers/gpu/drm/i915/intel_overlay.c:819:29: 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-09-06 19:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-06 19:01 [PATCH 1/2] drm/i915/overlay: Allocate physical registers from stolen Chris Wilson
2018-09-06 19:01 ` [PATCH 2/2] drm/i915/overlay: Use the ioctl parameters directly Chris Wilson
2018-09-11 13:12 ` Ville Syrjälä
2018-09-06 19:29 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/2] drm/i915/overlay: Allocate physical registers from stolen Patchwork
2018-09-06 19:29 ` Patchwork [this message]
2018-09-06 19:52 ` ✓ Fi.CI.BAT: success " Patchwork
2018-09-06 20:43 ` ✓ Fi.CI.IGT: " Patchwork
2018-09-11 13:07 ` [PATCH 1/2] " Ville Syrjälä
2018-09-11 13:13 ` Chris Wilson
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=20180906192948.5277.80772@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