From: Patchwork <patchwork@emeril.freedesktop.org>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✓ Fi.CI.IGT: success for drm/atomic-helper: check that drivers call drm_crtc_vblank_off (rev2)
Date: Wed, 18 Oct 2017 03:30:18 -0000 [thread overview]
Message-ID: <20171018033018.5903.89709@emeril.freedesktop.org> (raw)
In-Reply-To: <20171017145939.438-1-daniel.vetter@ffwll.ch>
== Series Details ==
Series: drm/atomic-helper: check that drivers call drm_crtc_vblank_off (rev2)
URL : https://patchwork.freedesktop.org/series/32141/
State : success
== Summary ==
Test perf:
Subgroup oa-exponents:
pass -> FAIL (shard-hsw) fdo#102254
Test kms_setmode:
Subgroup basic:
fail -> PASS (shard-hsw) fdo#99912
Test kms_cursor_legacy:
Subgroup cursor-vs-flip-atomic-transitions:
fail -> PASS (shard-hsw)
fdo#102254 https://bugs.freedesktop.org/show_bug.cgi?id=102254
fdo#99912 https://bugs.freedesktop.org/show_bug.cgi?id=99912
shard-hsw total:2553 pass:1440 dwarn:0 dfail:0 fail:10 skip:1103 time:9330s
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_6077/shards.html
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2017-10-18 3:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-17 14:59 [PATCH] drm/atomic-helper: check that drivers call drm_crtc_vblank_off Daniel Vetter
2017-10-17 15:11 ` Ville Syrjälä
2017-10-17 15:27 ` Daniel Vetter
2017-10-17 15:32 ` Ville Syrjälä
2017-10-18 8:23 ` Daniel Vetter
2017-10-17 16:25 ` ✓ Fi.CI.BAT: success for drm/atomic-helper: check that drivers call drm_crtc_vblank_off (rev2) Patchwork
2017-10-17 17:47 ` [PATCH] drm/atomic-helper: check that drivers call drm_crtc_vblank_off Sean Paul
2017-10-17 17:48 ` Sean Paul
2017-10-18 3:30 ` 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=20171018033018.5903.89709@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=daniel.vetter@ffwll.ch \
--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