From: Patchwork <patchwork@emeril.freedesktop.org>
To: Jani Nikula <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.SPARSE: warning for series starting with [RFC,1/2] drm/i915: start moving state checker to intel_verify.c
Date: Tue, 16 Apr 2019 12:15:52 -0000 [thread overview]
Message-ID: <20190416121552.29218.89072@emeril.freedesktop.org> (raw)
In-Reply-To: <20190416103603.8266-1-jani.nikula@intel.com>
== Series Details ==
Series: series starting with [RFC,1/2] drm/i915: start moving state checker to intel_verify.c
URL : https://patchwork.freedesktop.org/series/59569/
State : warning
== Summary ==
$ dim sparse origin/drm-tip
Sparse version: v0.5.2
Commit: drm/i915: start moving state checker to intel_verify.c
+./include/uapi/linux/perf_event.h:147:56: warning: cast truncates bits from constant value (8000000000000000 becomes 0)
Commit: drm/i915: move pipe config compare to intel_verify.c
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-04-16 12:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 10:36 [RFC 1/2] drm/i915: start moving state checker to intel_verify.c Jani Nikula
2019-04-16 10:36 ` [RFC 2/2] drm/i915: move pipe config compare " Jani Nikula
2019-05-15 9:36 ` Daniel Vetter
2019-04-16 12:14 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [RFC,1/2] drm/i915: start moving state checker " Patchwork
2019-04-16 12:15 ` Patchwork [this message]
2019-04-16 12:42 ` ✓ Fi.CI.BAT: success " Patchwork
2019-04-16 17:45 ` ✓ Fi.CI.IGT: " Patchwork
2019-05-15 9:33 ` [RFC 1/2] " Daniel Vetter
2019-05-15 9:38 ` Daniel Vetter
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=20190416121552.29218.89072@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@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).