From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Matthew Brost" <matthew.brost@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/execlists: Weak parallel submission support for execlists
Date: Thu, 21 Oct 2021 00:53:59 -0000 [thread overview]
Message-ID: <163477763993.20178.7028880740591998156@emeril.freedesktop.org> (raw)
In-Reply-To: <20211020214751.34602-1-matthew.brost@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1747 bytes --]
== Series Details ==
Series: drm/i915/execlists: Weak parallel submission support for execlists
URL : https://patchwork.freedesktop.org/series/96088/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10767 -> Patchwork_21398
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21398/index.html
Known issues
------------
Here are the changes found in Patchwork_21398 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@kms_frontbuffer_tracking@basic:
- fi-cml-u2: [PASS][1] -> [DMESG-WARN][2] ([i915#4269])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10767/fi-cml-u2/igt@kms_frontbuffer_tracking@basic.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21398/fi-cml-u2/igt@kms_frontbuffer_tracking@basic.html
[i915#4269]: https://gitlab.freedesktop.org/drm/intel/issues/4269
Participating hosts (41 -> 37)
------------------------------
Missing (4): fi-ctg-p8600 fi-bsw-cyan bat-dg1-6 fi-hsw-4200u
Build changes
-------------
* Linux: CI_DRM_10767 -> Patchwork_21398
CI-20190529: 20190529
CI_DRM_10767: 4d947bb057406e5c30081736db70da3f5726e0cd @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_6258: 4c80c71d7dec29b6376846ae96bd04dc0b6e34d9 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_21398: a7325f8bdd56fe264255b44f93be2ddda1b3929f @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
a7325f8bdd56 drm/i915/execlists: Weak parallel submission support for execlists
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21398/index.html
[-- Attachment #2: Type: text/html, Size: 2339 bytes --]
next prev parent reply other threads:[~2021-10-21 0:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-20 21:47 [PATCH] drm/i915/execlists: Weak parallel submission support for execlists Matthew Brost
2021-10-20 21:47 ` [Intel-gfx] " Matthew Brost
2021-10-21 0:53 ` Patchwork [this message]
2021-10-21 6:14 ` [Intel-gfx] ✓ Fi.CI.IGT: success for " Patchwork
2021-10-26 21:58 ` [PATCH] " John Harrison
2021-10-26 21:58 ` [Intel-gfx] " John Harrison
2021-10-27 19:17 ` Matthew Brost
2021-10-27 19:17 ` [Intel-gfx] " Matthew Brost
2021-10-27 20:04 ` John Harrison
2021-10-27 20:04 ` [Intel-gfx] " John Harrison
2021-10-27 20:10 ` Matthew Brost
2021-10-27 20:10 ` [Intel-gfx] " Matthew Brost
2021-11-01 10:35 ` Tvrtko Ursulin
2021-11-01 10:35 ` Tvrtko Ursulin
2021-11-11 16:49 ` Matthew Brost
2021-11-11 16:49 ` Matthew Brost
2021-11-12 14:13 ` Tvrtko Ursulin
2021-11-12 14:13 ` Tvrtko Ursulin
2021-11-12 17:59 ` Matthew Brost
2021-11-12 17:59 ` Matthew Brost
2021-11-15 10:34 ` Tvrtko Ursulin
2021-11-15 10:34 ` Tvrtko Ursulin
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=163477763993.20178.7028880740591998156@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.brost@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.