From: Patchwork <patchwork@emeril.freedesktop.org>
To: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.SPARSE: warning for split out intel_display_power
Date: Fri, 31 May 2019 22:52:09 -0000 [thread overview]
Message-ID: <20190531225209.20999.22678@emeril.freedesktop.org> (raw)
In-Reply-To: <20190531222409.9177-1-daniele.ceraolospurio@intel.com>
== Series Details ==
Series: split out intel_display_power
URL : https://patchwork.freedesktop.org/series/61453/
State : warning
== Summary ==
$ dim sparse origin/drm-tip
Sparse version: v0.5.2
Commit: drm/i915: extract intel_display_power.h/c from intel_runtime_pm.h/c
+./include/uapi/linux/perf_event.h:147:56: warning: cast truncates bits from constant value (8000000000000000 becomes 0)
Commit: drm/i915: move more defs in intel_display_power.h
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-05-31 22:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-31 22:24 [PATCH 0/2] split out intel_display_power Daniele Ceraolo Spurio
2019-05-31 22:24 ` [PATCH 1/2] drm/i915: extract intel_display_power.h/c from intel_runtime_pm.h/c Daniele Ceraolo Spurio
2019-06-01 8:45 ` Chris Wilson
2019-05-31 22:24 ` [PATCH 2/2] drm/i915: move more defs in intel_display_power.h Daniele Ceraolo Spurio
2019-06-01 8:46 ` Chris Wilson
2019-05-31 22:50 ` ✗ Fi.CI.CHECKPATCH: warning for split out intel_display_power Patchwork
2019-05-31 22:52 ` Patchwork [this message]
2019-05-31 23:30 ` ✓ Fi.CI.BAT: success " Patchwork
2019-06-01 8:45 ` [PATCH 0/2] " Chris Wilson
2019-06-03 18:43 ` Jani Nikula
2019-06-04 7:12 ` Imre Deak
2019-06-04 7:34 ` Chris Wilson
2019-06-02 3:36 ` ✗ Fi.CI.IGT: failure for " 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=20190531225209.20999.22678@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=daniele.ceraolospurio@intel.com \
--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