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 series starting with [1/2] drm/i915/execlists: Delay updating ring register state after resume (rev2)
Date: Thu, 16 Aug 2018 20:09:03 -0000 [thread overview]
Message-ID: <20180816200903.29042.42052@emeril.freedesktop.org> (raw)
In-Reply-To: <20180816111149.31403-1-chris@chris-wilson.co.uk>
== Series Details ==
Series: series starting with [1/2] drm/i915/execlists: Delay updating ring register state after resume (rev2)
URL : https://patchwork.freedesktop.org/series/48310/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_4680_full -> Patchwork_9964_full =
== Summary - SUCCESS ==
No regressions found.
== Changes ==
No changes found
== Participating hosts (5 -> 5) ==
No changes in participating hosts
== Build changes ==
* Linux: CI_DRM_4680 -> Patchwork_9964
CI_DRM_4680: c0adc75a6340ba5a3f9cf07c5064627ee73b9ba9 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_4603: 1598fdb717546e25e8077935daa8e97768ad245d @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_9964: b4088e6d50cf60b7cd68152b5a81bf7d7ad77128 @ git://anongit.freedesktop.org/gfx-ci/linux
piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ git://anongit.freedesktop.org/piglit
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_9964/shards.html
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-08-16 20:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-16 11:11 [PATCH 1/2] drm/i915/execlists: Delay updating ring register state after resume Chris Wilson
2018-08-16 11:11 ` [PATCH 2/2] drm/i915/execlists: Use coherent writes into the context image Chris Wilson
2018-08-16 11:54 ` Chris Wilson
2018-08-16 15:49 ` [PATCH v2] " Chris Wilson
2018-08-16 11:19 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/2] drm/i915/execlists: Delay updating ring register state after resume Patchwork
2018-08-16 11:20 ` ✗ Fi.CI.SPARSE: " Patchwork
2018-08-16 11:36 ` ✗ Fi.CI.BAT: failure " Patchwork
2018-08-16 16:25 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/2] drm/i915/execlists: Delay updating ring register state after resume (rev2) Patchwork
2018-08-16 16:26 ` ✗ Fi.CI.SPARSE: " Patchwork
2018-08-16 16:43 ` ✓ Fi.CI.BAT: success " Patchwork
2018-08-16 20:09 ` Patchwork [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-09-13 17:32 [PATCH 1/2] drm/i915/execlists: Delay updating ring register state after resume Chris Wilson
2018-09-13 23:02 ` ✓ Fi.CI.IGT: success for series starting with [1/2] drm/i915/execlists: Delay updating ring register state after resume (rev2) 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=20180816200903.29042.42052@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).