From: Patchwork <patchwork@emeril.freedesktop.org>
To: "José Roberto de Souza" <jose.souza@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.SPARSE: warning for series starting with [v3,1/2] drm/i915: Add HAS_DISPLAY() and use it (rev2)
Date: Mon, 03 Dec 2018 18:23:03 -0000 [thread overview]
Message-ID: <20181203182303.3446.58808@emeril.freedesktop.org> (raw)
In-Reply-To: <20181130232048.14216-1-jose.souza@intel.com>
== Series Details ==
Series: series starting with [v3,1/2] drm/i915: Add HAS_DISPLAY() and use it (rev2)
URL : https://patchwork.freedesktop.org/series/53341/
State : warning
== Summary ==
$ dim sparse origin/drm-tip
Sparse version: v0.5.2
Commit: drm/i915: Add HAS_DISPLAY() and use it
-drivers/gpu/drm/i915/selftests/../i915_drv.h:3571:16: warning: expression using sizeof(void)
+drivers/gpu/drm/i915/selftests/../i915_drv.h:3573:16: warning: expression using sizeof(void)
Commit: drm/i915: Move display device info capabilities to its own struct
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-03 18:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-30 23:20 [PATCH v3 1/2] drm/i915: Add HAS_DISPLAY() and use it José Roberto de Souza
2018-11-30 23:20 ` [PATCH v3 2/2] drm/i915: Move display device info capabilities to its own struct José Roberto de Souza
2018-11-30 23:32 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [v3,1/2] drm/i915: Add HAS_DISPLAY() and use it Patchwork
2018-11-30 23:34 ` ✗ Fi.CI.SPARSE: " Patchwork
2018-11-30 23:52 ` ✓ Fi.CI.BAT: success " Patchwork
2018-12-01 18:32 ` ✗ Fi.CI.IGT: failure " Patchwork
2018-12-03 23:00 ` Souza, Jose
2018-12-03 18:21 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [v3,1/2] drm/i915: Add HAS_DISPLAY() and use it (rev2) Patchwork
2018-12-03 18:23 ` Patchwork [this message]
2018-12-04 8:38 ` ✓ Fi.CI.BAT: success " Patchwork
2018-12-04 10:34 ` ✓ 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=20181203182303.3446.58808@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jose.souza@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