From: Patchwork <patchwork@emeril.freedesktop.org>
To: Matt Roper <matthew.d.roper@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.SPARSE: warning for series starting with [v2,1/2] drm/i915: Use intel_ types more consistently for watermark code (v2)
Date: Mon, 10 Dec 2018 22:06:54 -0000 [thread overview]
Message-ID: <20181210220654.15482.87550@emeril.freedesktop.org> (raw)
In-Reply-To: <20181210215415.19854-1-matthew.d.roper@intel.com>
== Series Details ==
Series: series starting with [v2,1/2] drm/i915: Use intel_ types more consistently for watermark code (v2)
URL : https://patchwork.freedesktop.org/series/53859/
State : warning
== Summary ==
$ dim sparse origin/drm-tip
Sparse version: v0.5.2
Commit: drm/i915: Use intel_ types more consistently for watermark code (v2)
-drivers/gpu/drm/i915/selftests/../i915_drv.h:3563:16: warning: expression using sizeof(void)
+drivers/gpu/drm/i915/selftests/../i915_drv.h:3561:16: warning: expression using sizeof(void)
Commit: drm/i915: Use intel_ types more consistently for color management code (v2)
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-10 22:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-10 21:54 [PATCH v2 1/2] drm/i915: Use intel_ types more consistently for watermark code (v2) Matt Roper
2018-12-10 21:54 ` [PATCH v2 2/2] drm/i915: Use intel_ types more consistently for color management " Matt Roper
2018-12-10 22:05 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [v2,1/2] drm/i915: Use intel_ types more consistently for watermark " Patchwork
2018-12-10 22:06 ` Patchwork [this message]
2018-12-10 22:20 ` ✓ Fi.CI.BAT: success " Patchwork
2018-12-11 0:44 ` ✓ 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=20181210220654.15482.87550@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.d.roper@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