From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Chris Wilson" <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/gem: Lazily acquire the device wakeref for freeing objects
Date: Fri, 24 Apr 2020 16:12:07 -0000 [thread overview]
Message-ID: <158774472769.10800.9652449085883863613@emeril.freedesktop.org> (raw)
In-Reply-To: <20200424152412.5928-1-chris@chris-wilson.co.uk>
== Series Details ==
Series: drm/i915/gem: Lazily acquire the device wakeref for freeing objects
URL : https://patchwork.freedesktop.org/series/76440/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8360 -> Patchwork_17453
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17453/index.html
Known issues
------------
Here are the changes found in Patchwork_17453 that come from known issues:
### IGT changes ###
#### Possible fixes ####
* igt@i915_selftest@live@execlists:
- fi-cml-s: [INCOMPLETE][1] -> [PASS][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8360/fi-cml-s/igt@i915_selftest@live@execlists.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17453/fi-cml-s/igt@i915_selftest@live@execlists.html
* igt@i915_selftest@live@gt_timelines:
- fi-bwr-2160: [INCOMPLETE][3] ([i915#489]) -> [PASS][4]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8360/fi-bwr-2160/igt@i915_selftest@live@gt_timelines.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17453/fi-bwr-2160/igt@i915_selftest@live@gt_timelines.html
[i915#489]: https://gitlab.freedesktop.org/drm/intel/issues/489
Participating hosts (48 -> 43)
------------------------------
Additional (1): fi-kbl-7500u
Missing (6): fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-ctg-p8600 fi-byt-clapper fi-bdw-samus
Build changes
-------------
* CI: CI-20190529 -> None
* Linux: CI_DRM_8360 -> Patchwork_17453
CI-20190529: 20190529
CI_DRM_8360: 034e1ba4afede6e10ef50596f891b7ff85f4ae22 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5610: 71fed15724898a8f914666093352a964b70a62fc @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_17453: 06a8555045e20cde4126faf363592728f2a2d69f @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
06a8555045e2 drm/i915/gem: Lazily acquire the device wakeref for freeing objects
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17453/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-04-24 16:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-24 15:24 [Intel-gfx] [PATCH] drm/i915/gem: Lazily acquire the device wakeref for freeing objects Chris Wilson
2020-04-24 16:01 ` Janusz Krzysztofik
2020-04-24 16:12 ` Patchwork [this message]
2020-04-24 18:42 ` [Intel-gfx] ✓ Fi.CI.IGT: success for " Patchwork
2020-04-28 9:53 ` [Intel-gfx] [PATCH] " Janusz Krzysztofik
2020-04-28 9:55 ` Chris Wilson
2020-04-28 12:45 ` Janusz Krzysztofik
2020-04-28 12:59 ` Chris Wilson
2020-04-28 14:35 ` Janusz Krzysztofik
2020-04-28 14:48 ` Chris Wilson
2020-04-28 15:30 ` Janusz Krzysztofik
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=158774472769.10800.9652449085883863613@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 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.