From: Patchwork <patchwork@emeril.freedesktop.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✓ Fi.CI.BAT: success for series starting with [1/2] drm/i915: Stop overwriting RING_IMR in rcs resume
Date: Thu, 18 Apr 2019 16:30:31 -0000 [thread overview]
Message-ID: <20190418163031.29095.78314@emeril.freedesktop.org> (raw)
In-Reply-To: <20190418132720.3716-1-chris@chris-wilson.co.uk>
== Series Details ==
Series: series starting with [1/2] drm/i915: Stop overwriting RING_IMR in rcs resume
URL : https://patchwork.freedesktop.org/series/59713/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5953 -> Patchwork_12834
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://patchwork.freedesktop.org/api/1.0/series/59713/revisions/1/mbox/
Known issues
------------
Here are the changes found in Patchwork_12834 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@i915_selftest@live_contexts:
- fi-bdw-gvtdvm: PASS -> DMESG-FAIL [fdo#110235 ]
* igt@kms_cursor_legacy@basic-flip-after-cursor-varying-size:
- fi-glk-dsi: PASS -> INCOMPLETE [fdo#103359] / [k.org#198133]
#### Possible fixes ####
* igt@kms_pipe_crc_basic@read-crc-pipe-b:
- fi-byt-clapper: FAIL [fdo#103191] -> PASS +1
[fdo#103191]: https://bugs.freedesktop.org/show_bug.cgi?id=103191
[fdo#103359]: https://bugs.freedesktop.org/show_bug.cgi?id=103359
[fdo#110235 ]: https://bugs.freedesktop.org/show_bug.cgi?id=110235
[k.org#198133]: https://bugzilla.kernel.org/show_bug.cgi?id=198133
Participating hosts (50 -> 33)
------------------------------
Missing (17): fi-ilk-m540 fi-bxt-dsi fi-bsw-n3050 fi-byt-j1900 fi-byt-squawks fi-icl-u2 fi-bsw-cyan fi-apl-guc fi-kbl-guc fi-ctg-p8600 fi-hsw-4770 fi-bxt-j4205 fi-icl-y fi-bdw-samus fi-bsw-kefka fi-skl-6700k2 fi-kbl-r
Build changes
-------------
* Linux: CI_DRM_5953 -> Patchwork_12834
CI_DRM_5953: 7ab8969b77f4f10172e3836b6d5c1d917f7e4007 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_4957: a765aa108105804c19096554447ad0cb71f64fc3 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_12834: a7a8a8552578ec852ffa5e7eaebe80ef55e1a701 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
a7a8a8552578 drm/i915: Setup the RCS ring prior to execution
a6025c2c32ab drm/i915: Stop overwriting RING_IMR in rcs resume
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_12834/
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-04-18 16:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-18 13:27 [PATCH 1/2] drm/i915: Stop overwriting RING_IMR in rcs resume Chris Wilson
2019-04-18 13:27 ` [PATCH 2/2] drm/i915: Setup the RCS ring prior to execution Chris Wilson
2019-04-18 15:10 ` Tvrtko Ursulin
2019-04-18 14:34 ` [PATCH 1/2] drm/i915: Stop overwriting RING_IMR in rcs resume Tvrtko Ursulin
2019-04-18 14:59 ` Chris Wilson
2019-04-18 15:08 ` Tvrtko Ursulin
2019-04-18 15:14 ` Chris Wilson
2019-04-18 16:30 ` Patchwork [this message]
2019-04-18 18:07 ` ✓ Fi.CI.IGT: success for series starting with [1/2] " 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=20190418163031.29095.78314@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