intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✓ Fi.CI.IGT: success for drm/i915: Read ilk FDI PLL frequency once during initialisation
Date: Sun, 05 Nov 2017 15:23:28 -0000	[thread overview]
Message-ID: <20171105152328.4569.2604@emeril.freedesktop.org> (raw)
In-Reply-To: <20171105134905.4636-1-chris@chris-wilson.co.uk>

== Series Details ==

Series: drm/i915: Read ilk FDI PLL frequency once during initialisation
URL   : https://patchwork.freedesktop.org/series/33210/
State : success

== Summary ==

Test kms_setmode:
        Subgroup basic:
                pass       -> FAIL       (shard-hsw) fdo#99912

fdo#99912 https://bugs.freedesktop.org/show_bug.cgi?id=99912

shard-hsw        total:2539 pass:1433 dwarn:0   dfail:0   fail:9   skip:1097 time:9228s

== Logs ==

For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_6967/shards.html
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2017-11-05 15:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-05 13:49 [PATCH] drm/i915: Read ilk FDI PLL frequency once during initialisation Chris Wilson
2017-11-05 14:36 ` ✓ Fi.CI.BAT: success for " Patchwork
2017-11-05 15:23 ` Patchwork [this message]
2017-11-07 21:25 ` [PATCH] " Ville Syrjälä
2017-11-07 21:47 ` [PATCH v2] " Chris Wilson
2017-11-08  7:47   ` Maarten Lankhorst
2017-11-08  9:24     ` Chris Wilson
2017-11-08 11:22   ` Ville Syrjälä
2017-11-08 15:48     ` Chris Wilson
2017-11-08  9:48 ` ✓ Fi.CI.BAT: success for drm/i915: Read ilk FDI PLL frequency once during initialisation (rev2) Patchwork
2017-11-08 10:50 ` ✓ Fi.CI.IGT: " 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=20171105152328.4569.2604@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=chris@chris-wilson.co.uk \
    --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;
as well as URLs for NNTP newsgroup(s).