From: Patchwork <patchwork@emeril.freedesktop.org>
To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✓ Ro.CI.BAT: success for Fix looking at encoder->type in debugfs.
Date: Mon, 20 Jun 2016 14:17:20 -0000 [thread overview]
Message-ID: <20160620141720.16093.9999@emeril.freedesktop.org> (raw)
In-Reply-To: <1466431059-8919-1-git-send-email-maarten.lankhorst@linux.intel.com>
== Series Details ==
Series: Fix looking at encoder->type in debugfs.
URL : https://patchwork.freedesktop.org/series/8926/
State : success
== Summary ==
Series 8926v1 Fix looking at encoder->type in debugfs.
http://patchwork.freedesktop.org/api/1.0/series/8926/revisions/1/mbox
fi-skl-i7-6700k total:223 pass:186 dwarn:0 dfail:0 fail:2 skip:35
ro-bdw-i7-5600u total:223 pass:183 dwarn:0 dfail:0 fail:2 skip:38
ro-bsw-n3050 total:223 pass:170 dwarn:0 dfail:0 fail:4 skip:49
ro-byt-n2820 total:223 pass:171 dwarn:0 dfail:0 fail:5 skip:47
ro-ilk1-i5-650 total:218 pass:148 dwarn:0 dfail:0 fail:3 skip:67
ro-ivb2-i7-3770 total:223 pass:183 dwarn:0 dfail:0 fail:2 skip:38
ro-skl3-i5-6260u total:223 pass:199 dwarn:1 dfail:0 fail:2 skip:21
ro-snb-i7-2620M total:223 pass:172 dwarn:0 dfail:0 fail:3 skip:48
fi-hsw-i7-4770k failed to connect after reboot
fi-skl-i5-6260u failed to connect after reboot
fi-snb-i7-2600 failed to connect after reboot
ro-bdw-i5-5250u failed to connect after reboot
ro-bdw-i7-5557U failed to connect after reboot
ro-hsw-i3-4010u failed to connect after reboot
ro-hsw-i7-4770r failed to connect after reboot
ro-ilk-i7-620lm failed to connect after reboot
ro-ivb-i7-3770 failed to connect after reboot
Results at /archive/results/CI_IGT_test/RO_Patchwork_1238/
f586720 drm-intel-nightly: 2016y-06m-20d-13h-24m-46s UTC integration manifest
7b2831b drm/i915: Use connector_type for printing in intel_connector_info
400c93d drm/i915: Use atomic state and connector_type in i915_sink_src
6c4e767 drm/i915: Use connector_type instead of intel_encoder->type for DP.
83ded8c drm/i915: Use connector->name in drrs debugfs.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2016-06-20 14:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-20 13:57 [PATCH 0/4] Fix looking at encoder->type in debugfs Maarten Lankhorst
2016-06-20 13:57 ` [PATCH 1/4] drm/i915: Use connector->name in drrs debugfs Maarten Lankhorst
2016-06-20 13:57 ` [PATCH 2/4] drm/i915: Use connector_type instead of intel_encoder->type for DP Maarten Lankhorst
2016-06-20 13:57 ` [PATCH 3/4] drm/i915: Use atomic state and connector_type in i915_sink_src Maarten Lankhorst
2016-06-20 13:57 ` [PATCH 4/4] drm/i915: Use connector_type for printing in intel_connector_info Maarten Lankhorst
2016-06-20 15:04 ` Ville Syrjälä
2016-06-21 10:00 ` [PATCH v2 4/4] drm/i915: Use connector_type for printing in intel_connector_info, v2 Maarten Lankhorst
2016-06-20 14:17 ` 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=20160620141720.16093.9999@emeril.freedesktop.org \
--to=patchwork@emeril.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