From: Patchwork <patchwork@annarchy.freedesktop.org>
To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✓ Fi.CI.BAT: success for drm/atomic: Allow for holes in connector state, v2.
Date: Wed, 17 Feb 2016 09:51:01 -0000 [thread overview]
Message-ID: <20160217095101.18088.64770@annarchy.freedesktop.org> (raw)
In-Reply-To: <1455694325-24989-1-git-send-email-maarten.lankhorst@linux.intel.com>
== Summary ==
Series 3514v1 drm/atomic: Allow for holes in connector state, v2.
http://patchwork.freedesktop.org/api/1.0/series/3514/revisions/1/mbox/
Test kms_flip:
Subgroup basic-flip-vs-dpms:
pass -> DMESG-WARN (ilk-hp8440p) UNSTABLE
Test pm_rpm:
Subgroup basic-pci-d3-state:
dmesg-warn -> PASS (byt-nuc)
byt-nuc total:165 pass:141 dwarn:0 dfail:0 fail:0 skip:24
ilk-hp8440p total:165 pass:115 dwarn:1 dfail:0 fail:1 skip:48
snb-x220t total:165 pass:142 dwarn:0 dfail:0 fail:2 skip:21
Results at /archive/results/CI_IGT_test/Patchwork_1421/
bd0b1a9aa8b7fdb2e06a5cbf1756ef93de2fa3fd drm-intel-nightly: 2016y-02m-16d-17h-53m-05s UTC integration manifest
d8fd198f83edf12cb2611f483585350a77a2ccb3 drm/atomic: Allow for holes in connector state, v2.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-02-17 9:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-17 7:32 [PATCH v2] drm/atomic: Allow for holes in connector state, v2 Maarten Lankhorst
2016-02-17 9:51 ` Patchwork [this message]
2016-02-17 15:33 ` [v2] " Lyude
2016-02-17 19:24 ` [PATCH v2] " Ville Syrjälä
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=20160217095101.18088.64770@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).