From: Patchwork <patchwork@emeril.freedesktop.org>
To: Jani Nikula <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✓ Fi.CI.BAT: success for series starting with [v2,1/3] drm/i915/csr: keep firmware name and required version together
Date: Fri, 07 Sep 2018 12:57:18 -0000 [thread overview]
Message-ID: <20180907125718.6599.17656@emeril.freedesktop.org> (raw)
In-Reply-To: <20180906104033.20872-1-jani.nikula@intel.com>
== Series Details ==
Series: series starting with [v2,1/3] drm/i915/csr: keep firmware name and required version together
URL : https://patchwork.freedesktop.org/series/49269/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_4786 -> Patchwork_10126 =
== Summary - SUCCESS ==
No regressions found.
External URL: https://patchwork.freedesktop.org/api/1.0/series/49269/revisions/1/mbox/
== Known issues ==
Here are the changes found in Patchwork_10126 that come from known issues:
=== IGT changes ===
==== Issues hit ====
igt@drv_module_reload@basic-reload:
fi-blb-e6850: PASS -> INCOMPLETE (fdo#107718)
==== Possible fixes ====
igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a:
fi-byt-clapper: FAIL (fdo#107362, fdo#103191) -> PASS
igt@kms_psr@primary_page_flip:
fi-kbl-r: FAIL (fdo#107336) -> PASS
fdo#103191 https://bugs.freedesktop.org/show_bug.cgi?id=103191
fdo#107336 https://bugs.freedesktop.org/show_bug.cgi?id=107336
fdo#107362 https://bugs.freedesktop.org/show_bug.cgi?id=107362
fdo#107718 https://bugs.freedesktop.org/show_bug.cgi?id=107718
== Participating hosts (54 -> 48) ==
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_4786 -> Patchwork_10126
CI_DRM_4786: d28dcb05a3c33df6fcb0828d81fa0bb6591a97be @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_4634: 7d89cc39dde3b4881d85ace45d504cc098fa3684 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_10126: 8ad14e2e5b1fdea88dfc32e1825314d767aebf58 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
8ad14e2e5b1f drm/i915/csr: bypass firmware request on i915.dmc_firmware_path=""
dfaef5add127 drm/i915/csr: keep max firmware size together with firmare name and version
e5309b975cf4 drm/i915/csr: keep firmware name and required version together
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_10126/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-09-07 12:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-06 10:40 [PATCH v2 1/3] drm/i915/csr: keep firmware name and required version together Jani Nikula
2018-09-06 10:40 ` [PATCH v2 2/3] drm/i915/csr: keep max firmware size together with firmare name and version Jani Nikula
2018-09-06 10:40 ` [PATCH v2 3/3] drm/i915/csr: bypass firmware request on i915.dmc_firmware_path="" Jani Nikula
2018-09-06 14:23 ` ✗ Fi.CI.SPARSE: warning for series starting with [v2,1/3] drm/i915/csr: keep firmware name and required version together Patchwork
2018-09-06 14:40 ` ✗ Fi.CI.BAT: failure " Patchwork
2018-09-07 12:57 ` Patchwork [this message]
2018-09-07 15:07 ` ✓ Fi.CI.IGT: success " 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=20180907125718.6599.17656@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox