All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: intel-gfx@lists.freedesktop.org, Dave Gordon <david.s.gordon@intel.com>
Subject: Re: ✓ Ro.CI.BAT: success for drm/i915/guc: don't ever forward VBlank to the GuC
Date: Mon, 27 Jun 2016 13:22:44 +0100	[thread overview]
Message-ID: <57711A94.20102@linux.intel.com> (raw)
In-Reply-To: <20160624152542.12912.86642@emeril.freedesktop.org>


On 24/06/16 16:25, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915/guc: don't ever forward VBlank to the GuC
> URL   : https://patchwork.freedesktop.org/series/9145/
> State : success
>
> == Summary ==
>
> Series 9145v1 drm/i915/guc: don't ever forward VBlank to the GuC
> http://patchwork.freedesktop.org/api/1.0/series/9145/revisions/1/mbox
>
> Test gem_exec_flush:
>          Subgroup basic-batch-kernel-default-cmd:
>                  fail       -> PASS       (ro-byt-n2820)
> Test kms_pipe_crc_basic:
>          Subgroup suspend-read-crc-pipe-b:
>                  dmesg-warn -> SKIP       (ro-bdw-i5-5250u)
>          Subgroup suspend-read-crc-pipe-c:
>                  dmesg-warn -> SKIP       (ro-bdw-i5-5250u)
>
> fi-hsw-i7-4770k  total:228  pass:194  dwarn:0   dfail:0   fail:1   skip:33
> fi-skl-i5-6260u  total:228  pass:202  dwarn:0   dfail:0   fail:1   skip:25
> fi-snb-i7-2600   total:228  pass:174  dwarn:0   dfail:0   fail:1   skip:53
> ro-bdw-i5-5250u  total:227  pass:201  dwarn:1   dfail:1   fail:1   skip:23
> ro-bdw-i7-5600u  total:227  pass:189  dwarn:0   dfail:1   fail:0   skip:37
> ro-bsw-n3050     total:227  pass:175  dwarn:1   dfail:1   fail:2   skip:48
> ro-byt-n2820     total:227  pass:178  dwarn:0   dfail:1   fail:3   skip:45
> ro-hsw-i3-4010u  total:227  pass:194  dwarn:0   dfail:1   fail:1   skip:31
> ro-hsw-i7-4770r  total:227  pass:194  dwarn:0   dfail:1   fail:1   skip:31
> ro-ilk-i7-620lm  total:227  pass:154  dwarn:0   dfail:1   fail:2   skip:70
> ro-ilk1-i5-650   total:222  pass:154  dwarn:0   dfail:1   fail:2   skip:65
> ro-ivb-i7-3770   total:227  pass:185  dwarn:0   dfail:1   fail:1   skip:40
> ro-ivb2-i7-3770  total:227  pass:189  dwarn:0   dfail:1   fail:1   skip:36
> ro-skl3-i5-6260u total:227  pass:205  dwarn:1   dfail:1   fail:1   skip:19
> ro-snb-i7-2620M  total:227  pass:178  dwarn:0   dfail:1   fail:1   skip:47
> fi-kbl-qkkr failed to connect after reboot
> fi-skl-i7-6700k failed to connect after reboot
> ro-bdw-i7-5557U failed to connect after reboot
>
> Results at /archive/results/CI_IGT_test/RO_Patchwork_1301/
>
> 66e29f4 drm-intel-nightly: 2016y-06m-24d-13h-47m-00s UTC integration manifest
> 403064e drm/i915/guc: don't ever forward VBlank to the GuC

Merged to dinq, thanks for the patch.

Regards,

Tvrtko

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2016-06-27 12:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-24 14:57 [PATCH v3] drm/i915/guc: don't ever forward VBlank to the GuC Dave Gordon
2016-06-24 15:25 ` ✓ Ro.CI.BAT: success for " Patchwork
2016-06-27 12:22   ` Tvrtko Ursulin [this message]
2016-06-27 12:19 ` [PATCH v3] " Tvrtko Ursulin

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=57711A94.20102@linux.intel.com \
    --to=tvrtko.ursulin@linux.intel.com \
    --cc=david.s.gordon@intel.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.