From: Patchwork <patchwork@emeril.freedesktop.org>
To: Shashank Sharma <shashank.sharma@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✓ Fi.CI.BAT: success for series starting with [v12,1/8] drm/i915: Introduce CRTC output format
Date: Fri, 12 Oct 2018 06:50:25 -0000 [thread overview]
Message-ID: <20181012065025.1371.98883@emeril.freedesktop.org> (raw)
In-Reply-To: <1539325394-20788-1-git-send-email-shashank.sharma@intel.com>
== Series Details ==
Series: series starting with [v12,1/8] drm/i915: Introduce CRTC output format
URL : https://patchwork.freedesktop.org/series/50897/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_4976 -> Patchwork_10433 =
== Summary - SUCCESS ==
No regressions found.
External URL: https://patchwork.freedesktop.org/api/1.0/series/50897/revisions/1/mbox/
== Known issues ==
Here are the changes found in Patchwork_10433 that come from known issues:
=== IGT changes ===
==== Possible fixes ====
igt@kms_flip@basic-flip-vs-modeset:
fi-glk-j4005: DMESG-WARN (fdo#106097) -> PASS
igt@kms_pipe_crc_basic@read-crc-pipe-c:
fi-skl-6700k2: FAIL (fdo#103191, fdo#107362) -> PASS
igt@pm_rpm@module-reload:
fi-skl-6600u: INCOMPLETE (fdo#107807) -> PASS
fi-glk-j4005: FAIL -> PASS
fdo#103191 https://bugs.freedesktop.org/show_bug.cgi?id=103191
fdo#106097 https://bugs.freedesktop.org/show_bug.cgi?id=106097
fdo#107362 https://bugs.freedesktop.org/show_bug.cgi?id=107362
fdo#107807 https://bugs.freedesktop.org/show_bug.cgi?id=107807
== Participating hosts (45 -> 40) ==
Missing (5): fi-ctg-p8600 fi-ilk-m540 fi-byt-squawks fi-bsw-cyan fi-icl-u
== Build changes ==
* Linux: CI_DRM_4976 -> Patchwork_10433
CI_DRM_4976: dec9886eff39d38332bb5ea438b9b053d6b2177c @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_4674: 93871c6fb3c25e5d350c9faf36ded917174214de @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_10433: 0503d0b7e9f84956e86f12d600a4bb33c8b4fb27 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
0503d0b7e9f8 drm/i915: Add YCBCR 4:2:0/4:4:4 support for LSPCON
cacda7f35a67 drm/i915: Write AVI infoframes for Parade LSPCON
1ddfe1f97e7f drm/i915: Write AVI infoframes for MCA LSPCON
adea576b594d drm/i915: Add AVI infoframe support for LSPCON
134878c5cb18 drm/i915: Check LSPCON vendor OUI
442a5056dd04 drm/i915: Add CRTC output format YCBCR 4:4:4
fbd32b6ad34e drm/i915: Add CRTC output format YCBCR 4:2:0
b69fba58f360 drm/i915: Introduce CRTC output format
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_10433/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-12 6:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-12 6:23 [PATCH v12 1/8] drm/i915: Introduce CRTC output format Shashank Sharma
2018-10-12 6:23 ` [PATCH v12 2/8] drm/i915: Add CRTC output format YCBCR 4:2:0 Shashank Sharma
2018-10-12 6:23 ` [PATCH v12 3/8] drm/i915: Add CRTC output format YCBCR 4:4:4 Shashank Sharma
2018-10-12 6:23 ` [PATCH v12 4/8] drm/i915: Check LSPCON vendor OUI Shashank Sharma
2018-10-12 6:23 ` [PATCH v12 5/8] drm/i915: Add AVI infoframe support for LSPCON Shashank Sharma
2018-10-12 6:23 ` [PATCH v12 6/8] drm/i915: Write AVI infoframes for MCA LSPCON Shashank Sharma
2018-10-12 6:23 ` [PATCH v12 7/8] drm/i915: Write AVI infoframes for Parade LSPCON Shashank Sharma
2018-10-12 6:23 ` [PATCH v12 8/8] drm/i915: Add YCBCR 4:2:0/4:4:4 support for LSPCON Shashank Sharma
2018-10-12 13:58 ` Ville Syrjälä
2018-10-12 17:51 ` Sharma, Shashank
2018-10-12 18:09 ` Ville Syrjälä
2018-10-12 18:32 ` Sharma, Shashank
2018-10-12 18:37 ` Ville Syrjälä
2018-10-15 13:12 ` Jani Nikula
2018-10-15 14:28 ` Sharma, Shashank
2018-10-12 6:34 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [v12,1/8] drm/i915: Introduce CRTC output format Patchwork
2018-10-12 6:50 ` Patchwork [this message]
2018-10-12 7:51 ` ✓ 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=20181012065025.1371.98883@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=shashank.sharma@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