From: Patchwork <patchwork@emeril.freedesktop.org>
To: Tvrtko Ursulin <tursulin@ursulin.net>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✓ Fi.CI.BAT: success for drm/i915/icl: Store available engine masks in INTEL_INFO
Date: Thu, 18 Oct 2018 11:11:58 -0000 [thread overview]
Message-ID: <20181018111158.3230.43459@emeril.freedesktop.org> (raw)
In-Reply-To: <20181018104106.30147-1-tvrtko.ursulin@linux.intel.com>
== Series Details ==
Series: drm/i915/icl: Store available engine masks in INTEL_INFO
URL : https://patchwork.freedesktop.org/series/51175/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_5005 -> Patchwork_10502 =
== Summary - SUCCESS ==
No regressions found.
External URL: https://patchwork.freedesktop.org/api/1.0/series/51175/revisions/1/mbox/
== Known issues ==
Here are the changes found in Patchwork_10502 that come from known issues:
=== IGT changes ===
==== Issues hit ====
igt@drv_module_reload@basic-reload:
fi-blb-e6850: PASS -> INCOMPLETE (fdo#107718)
igt@gem_exec_suspend@basic-s3:
fi-bdw-samus: NOTRUN -> INCOMPLETE (fdo#107773)
fi-kbl-soraka: NOTRUN -> INCOMPLETE (fdo#107774, fdo#107859, fdo#107556)
igt@kms_chamelium@hdmi-edid-read:
fi-icl-u2: NOTRUN -> DMESG-WARN (fdo#107732, fdo#108070)
igt@kms_chamelium@hdmi-hpd-fast:
fi-icl-u2: NOTRUN -> DMESG-WARN (fdo#107732)
igt@kms_frontbuffer_tracking@basic:
fi-hsw-peppy: PASS -> DMESG-WARN (fdo#102614)
fi-byt-clapper: PASS -> FAIL (fdo#103167)
fdo#102614 https://bugs.freedesktop.org/show_bug.cgi?id=102614
fdo#103167 https://bugs.freedesktop.org/show_bug.cgi?id=103167
fdo#107556 https://bugs.freedesktop.org/show_bug.cgi?id=107556
fdo#107718 https://bugs.freedesktop.org/show_bug.cgi?id=107718
fdo#107732 https://bugs.freedesktop.org/show_bug.cgi?id=107732
fdo#107773 https://bugs.freedesktop.org/show_bug.cgi?id=107773
fdo#107774 https://bugs.freedesktop.org/show_bug.cgi?id=107774
fdo#107859 https://bugs.freedesktop.org/show_bug.cgi?id=107859
fdo#108070 https://bugs.freedesktop.org/show_bug.cgi?id=108070
== Participating hosts (42 -> 42) ==
Additional (3): fi-kbl-soraka fi-icl-u2 fi-bdw-samus
Missing (3): fi-ilk-m540 fi-byt-squawks fi-bsw-cyan
== Build changes ==
* Linux: CI_DRM_5005 -> Patchwork_10502
CI_DRM_5005: 7a27ee6b5f714f6852abb0098990a05675bd9d55 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_4683: 7766b1e2348b32cc8ed58a972c6fd53b20279549 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_10502: 2316d11688a081d93c20a7065bb96f463b316a01 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
2316d11688a0 drm/i915/icl: Store available engine masks in INTEL_INFO
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_10502/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-10-18 11:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-18 10:41 [PATCH] drm/i915/icl: Store available engine masks in INTEL_INFO Tvrtko Ursulin
2018-10-18 11:11 ` Patchwork [this message]
2018-10-26 9:20 ` ✓ Fi.CI.BAT: success for " Tvrtko Ursulin
2018-10-18 18:46 ` [PATCH] " Daniele Ceraolo Spurio
2018-10-22 10:48 ` ✓ 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=20181018111158.3230.43459@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=tursulin@ursulin.net \
/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.