From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Zhao, Yakui" <yakui.zhao@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✓ Fi.CI.BAT: success for drm/i915: Use 64-bit write to optimize writing fence_reg on VGPU
Date: Tue, 03 Jul 2018 14:37:40 -0000 [thread overview]
Message-ID: <20180703143740.1439.57902@emeril.freedesktop.org> (raw)
In-Reply-To: <1530624467-29569-1-git-send-email-yakui.zhao@intel.com>
== Series Details ==
Series: drm/i915: Use 64-bit write to optimize writing fence_reg on VGPU
URL : https://patchwork.freedesktop.org/series/45841/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_4423 -> Patchwork_9510 =
== Summary - SUCCESS ==
No regressions found.
External URL: https://patchwork.freedesktop.org/api/1.0/series/45841/revisions/1/mbox/
== Known issues ==
Here are the changes found in Patchwork_9510 that come from known issues:
=== IGT changes ===
==== Issues hit ====
igt@kms_pipe_crc_basic@suspend-read-crc-pipe-c:
fi-bxt-dsi: NOTRUN -> INCOMPLETE (fdo#103927)
==== Possible fixes ====
igt@gem_exec_suspend@basic-s3:
{fi-cfl-8109u}: INCOMPLETE -> PASS
igt@kms_chamelium@dp-edid-read:
fi-kbl-7500u: FAIL (fdo#103841) -> PASS
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
fdo#103841 https://bugs.freedesktop.org/show_bug.cgi?id=103841
fdo#103927 https://bugs.freedesktop.org/show_bug.cgi?id=103927
== Participating hosts (45 -> 40) ==
Additional (1): fi-bxt-dsi
Missing (6): fi-ilk-m540 fi-hsw-4200u fi-hsw-peppy fi-byt-squawks fi-bsw-cyan fi-ctg-p8600
== Build changes ==
* Linux: CI_DRM_4423 -> Patchwork_9510
CI_DRM_4423: 9b9b45349fe3a36d41586992426d03a238396531 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_4533: 199220052af977598033d3810ffb4cc32d377522 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_9510: 8f3afb60f04c05b46289401cc19d38451fbf2c70 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
8f3afb60f04c drm/i915: Use 64-bit write to optimize writing fence_reg on VGPU
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_9510/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-07-03 14:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-03 13:27 [PATCH v3] drm/i915: Use 64-bit write to optimize writing fence_reg on VGPU Zhao Yakui
2018-07-03 13:32 ` Chris Wilson
2018-07-03 14:37 ` Patchwork [this message]
2018-07-03 23:33 ` ✓ Fi.CI.IGT: success for " 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=20180703143740.1439.57902@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=yakui.zhao@intel.com \
/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.