From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Anshuman Gupta" <anshuman.gupta@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✓ Fi.CI.BAT: success for HDCP minor refactoring (rev2)
Date: Mon, 18 May 2020 14:01:56 -0000 [thread overview]
Message-ID: <158981051668.31688.9118003973778422267@emeril.freedesktop.org> (raw)
In-Reply-To: <20200518111804.11842-1-anshuman.gupta@intel.com>
== Series Details ==
Series: HDCP minor refactoring (rev2)
URL : https://patchwork.freedesktop.org/series/77224/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8494 -> Patchwork_17688
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17688/index.html
Known issues
------------
Here are the changes found in Patchwork_17688 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@i915_selftest@live@gt_engines:
- fi-bwr-2160: [PASS][1] -> [INCOMPLETE][2] ([i915#489])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8494/fi-bwr-2160/igt@i915_selftest@live@gt_engines.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17688/fi-bwr-2160/igt@i915_selftest@live@gt_engines.html
#### Possible fixes ####
* igt@i915_selftest@live@execlists:
- fi-whl-u: [INCOMPLETE][3] ([i915#656]) -> [PASS][4]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8494/fi-whl-u/igt@i915_selftest@live@execlists.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17688/fi-whl-u/igt@i915_selftest@live@execlists.html
[i915#489]: https://gitlab.freedesktop.org/drm/intel/issues/489
[i915#656]: https://gitlab.freedesktop.org/drm/intel/issues/656
Participating hosts (51 -> 45)
------------------------------
Additional (1): fi-kbl-7560u
Missing (7): fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-ctg-p8600 fi-byt-clapper fi-bdw-samus
Build changes
-------------
* Linux: CI_DRM_8494 -> Patchwork_17688
CI-20190529: 20190529
CI_DRM_8494: 3d15348fde9b998e754da0b0655baf02b98e7f17 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5657: 649eae5c905a7460b44305800f95db83a6dd47cb @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_17688: 9fb88404f720d350f3e12c74344955b517dfb964 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
9fb88404f720 drm/i915/hdcp: No direct access to power_well desc
f30e23a85aeb drm/i915/hdcp: Add update_pipe early return
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17688/index.html
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-05-18 14:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-18 11:18 [Intel-gfx] [PATCH v2 0/2] HDCP minor refactoring Anshuman Gupta
2020-05-18 11:18 ` [Intel-gfx] [PATCH v2 1/2] drm/i915/hdcp: Add update_pipe early return Anshuman Gupta
2020-05-18 11:18 ` [Intel-gfx] [PATCH v2 2/2] drm/i915/hdcp: No direct access to power_well desc Anshuman Gupta
2020-05-18 14:01 ` Patchwork [this message]
2020-05-18 16:29 ` [Intel-gfx] ✓ Fi.CI.IGT: success for HDCP minor refactoring (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=158981051668.31688.9118003973778422267@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=anshuman.gupta@intel.com \
--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).