Patch Details
Series:drm/i915: Perform execbuffer object locking as a separate step
URL:https://patchwork.freedesktop.org/series/91506/
State:success
Details:https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20369/index.html

CI Bug Log - changes from CI_DRM_10225 -> Patchwork_20369

Summary

SUCCESS

No regressions found.

External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20369/index.html

Known issues

Here are the changes found in Patchwork_20369 that come from known issues:

IGT changes

Possible fixes

{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).

Participating hosts (48 -> 39)

Missing (9): fi-ilk-m540 fi-hsw-4200u fi-bsw-cyan bat-adlp-4 bat-adls-4 fi-ctg-p8600 bat-adls-3 fi-bdw-samus bat-jsl-1

Build changes

CI-20190529: 20190529
CI_DRM_10225: 52beaf52657f49ffda64af3c46548fb0907cf66d @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_6107: 2bec4e7619f04d2ca86006917acd3b5c86fb73a0 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_20369: 2e4245d2a116b28f046a6feb3fe16729725ae321 @ git://anongit.freedesktop.org/gfx-ci/linux

== Linux commits ==

2e4245d2a116 drm/i915: Perform execbuffer object locking as a separate step