From: Patchwork <patchwork@emeril.freedesktop.org>
To: Tvrtko Ursulin <tursulin@ursulin.net>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✓ Fi.CI.BAT: success for drm/i915/icl: Fix context RPCS programming
Date: Fri, 31 Aug 2018 12:23:59 -0000 [thread overview]
Message-ID: <20180831122359.24157.28531@emeril.freedesktop.org> (raw)
In-Reply-To: <20180831115334.2274-1-tvrtko.ursulin@linux.intel.com>
== Series Details ==
Series: drm/i915/icl: Fix context RPCS programming
URL : https://patchwork.freedesktop.org/series/49005/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_4748 -> Patchwork_10059 =
== Summary - SUCCESS ==
No regressions found.
External URL: https://patchwork.freedesktop.org/api/1.0/series/49005/revisions/1/mbox/
== Known issues ==
Here are the changes found in Patchwork_10059 that come from known issues:
=== IGT changes ===
==== Issues hit ====
igt@kms_frontbuffer_tracking@basic:
fi-hsw-peppy: PASS -> DMESG-WARN (fdo#102614)
{fi-byt-clapper}: PASS -> FAIL (fdo#103167)
==== Possible fixes ====
igt@kms_pipe_crc_basic@suspend-read-crc-pipe-c:
fi-bxt-dsi: INCOMPLETE (fdo#103927) -> PASS
{igt@kms_psr@primary_page_flip}:
fi-cnl-psr: FAIL (fdo#107336) -> PASS
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
fdo#102614 https://bugs.freedesktop.org/show_bug.cgi?id=102614
fdo#103167 https://bugs.freedesktop.org/show_bug.cgi?id=103167
fdo#103927 https://bugs.freedesktop.org/show_bug.cgi?id=103927
fdo#107336 https://bugs.freedesktop.org/show_bug.cgi?id=107336
== Participating hosts (53 -> 48) ==
Missing (5): fi-ctg-p8600 fi-ilk-m540 fi-byt-squawks fi-bsw-cyan fi-hsw-4200u
== Build changes ==
* Linux: CI_DRM_4748 -> Patchwork_10059
CI_DRM_4748: 6caeb081ceb9282503439565e7093c1032758289 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_4613: 3f89d7b02dcf662e994c7135b13d52bc8e09a4ea @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_10059: 8b03edf949e3c9c6d97154e40c11f1f0d2a1aec7 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
8b03edf949e3 drm/i915/icl: Fix context RPCS programming
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_10059/issues.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-31 12:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-31 11:53 [PATCH] drm/i915/icl: Fix context RPCS programming Tvrtko Ursulin
2018-08-31 12:07 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2018-08-31 12:23 ` Patchwork [this message]
2018-08-31 16:18 ` ✓ Fi.CI.IGT: success " Patchwork
2018-08-31 16:52 ` [PATCH] " Lionel Landwerlin
2018-09-03 11:11 ` Tvrtko Ursulin
2018-09-03 11:30 ` [PATCH v2] " Tvrtko Ursulin
2018-09-03 12:34 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915/icl: Fix context RPCS programming (rev2) Patchwork
2018-09-03 12:53 ` ✓ Fi.CI.BAT: success " Patchwork
2018-09-04 13:51 ` Tvrtko Ursulin
2018-09-03 17:36 ` ✓ 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=20180831122359.24157.28531@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=tursulin@ursulin.net \
/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