From: Patchwork <patchwork@annarchy.freedesktop.org>
To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.BAT: warning for Use more atomic state in i915.
Date: Wed, 17 Feb 2016 10:16:06 -0000 [thread overview]
Message-ID: <20160217101606.18089.6743@annarchy.freedesktop.org> (raw)
In-Reply-To: <1455697119-31416-1-git-send-email-maarten.lankhorst@linux.intel.com>
== Summary ==
Series 3515v1 Use more atomic state in i915.
http://patchwork.freedesktop.org/api/1.0/series/3515/revisions/1/mbox/
Test gem_ringfill:
Subgroup basic-default-hang:
incomplete -> PASS (snb-dellxps)
Test kms_flip:
Subgroup basic-flip-vs-dpms:
pass -> DMESG-WARN (ilk-hp8440p) UNSTABLE
Test kms_force_connector_basic:
Subgroup force-load-detect:
fail -> DMESG-FAIL (ilk-hp8440p)
Test kms_pipe_crc_basic:
Subgroup suspend-read-crc-pipe-a:
dmesg-warn -> PASS (skl-i5k-2)
Subgroup suspend-read-crc-pipe-c:
pass -> DMESG-WARN (skl-i5k-2)
dmesg-warn -> PASS (bsw-nuc-2)
Test pm_rpm:
Subgroup basic-pci-d3-state:
fail -> PASS (bdw-nuci7)
dmesg-warn -> PASS (byt-nuc)
Subgroup basic-rte:
dmesg-warn -> PASS (bsw-nuc-2)
bdw-nuci7 total:162 pass:152 dwarn:0 dfail:0 fail:0 skip:10
bdw-ultra total:165 pass:152 dwarn:0 dfail:0 fail:0 skip:13
bsw-nuc-2 total:165 pass:136 dwarn:0 dfail:0 fail:0 skip:29
byt-nuc total:165 pass:141 dwarn:0 dfail:0 fail:0 skip:24
hsw-brixbox total:165 pass:151 dwarn:0 dfail:0 fail:0 skip:14
ilk-hp8440p total:165 pass:115 dwarn:1 dfail:1 fail:0 skip:48
ivb-t430s total:165 pass:150 dwarn:0 dfail:0 fail:1 skip:14
skl-i5k-2 total:165 pass:149 dwarn:1 dfail:0 fail:0 skip:15
snb-dellxps total:165 pass:142 dwarn:0 dfail:0 fail:1 skip:22
Results at /archive/results/CI_IGT_test/Patchwork_1422/
bd0b1a9aa8b7fdb2e06a5cbf1756ef93de2fa3fd drm-intel-nightly: 2016y-02m-16d-17h-53m-05s UTC integration manifest
63594c947569ab29b704e598a04309083e1eb97f drm/i915: Use atomic state in intel_fb_initial_config.
449a002e8dee4e01290e7681139584e28d0c3cc7 drm/i915: Use correct dpms for intel_enable_crt.
e215b05e035b783bfe00165be36a7045fb97e395 drm/i915: Use atomic state in tv load detection.
56c9d06492c8693240dcfdb0f9617fb5f8bb07f2 drm/i915: Use atomic state for load detect in crt.
8489191ff8deab10d5ddbea70cac18c69d019bd8 drm/i915: Use atomic state to obtain load detection crtc, v3.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2016-02-17 10:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-17 8:18 [RESEND PATCH 0/5] Use more atomic state in i915 Maarten Lankhorst
2016-02-17 8:18 ` [RESEND PATCH 1/5] drm/i915: Use atomic state to obtain load detection crtc, v3 Maarten Lankhorst
2016-02-17 8:18 ` [RESEND PATCH 2/5] drm/i915: Use atomic state for load detect in crt Maarten Lankhorst
2016-02-17 8:18 ` [RESEND PATCH 3/5] drm/i915: Use atomic state in tv load detection Maarten Lankhorst
2016-02-17 8:18 ` [RESEND PATCH 4/5] drm/i915: Use correct dpms for intel_enable_crt Maarten Lankhorst
2016-02-17 8:18 ` [RESEND PATCH 5/5] drm/i915: Use atomic state in intel_fb_initial_config Maarten Lankhorst
2016-02-17 10:16 ` Patchwork [this message]
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=20160217101606.18089.6743@annarchy.freedesktop.org \
--to=patchwork@annarchy.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=maarten.lankhorst@linux.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).