From: Patchwork <patchwork@emeril.freedesktop.org>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✓ Fi.CI.IGT: success for series starting with [1/4] fbdev: Drop FBINFO_CAN_FORCE_OUTPUT flag
Date: Wed, 22 Aug 2018 10:09:36 -0000 [thread overview]
Message-ID: <20180822100936.30597.68075@emeril.freedesktop.org> (raw)
In-Reply-To: <20180822085405.10787-1-daniel.vetter@ffwll.ch>
== Series Details ==
Series: series starting with [1/4] fbdev: Drop FBINFO_CAN_FORCE_OUTPUT flag
URL : https://patchwork.freedesktop.org/series/48541/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_4695_full -> Patchwork_9987_full =
== Summary - SUCCESS ==
No regressions found.
== Known issues ==
Here are the changes found in Patchwork_9987_full that come from known issues:
=== IGT changes ===
==== Issues hit ====
igt@gem_ctx_isolation@vcs1-s3:
shard-kbl: PASS -> INCOMPLETE (fdo#103665)
igt@kms_available_modes_crc@available_mode_test_crc:
shard-kbl: NOTRUN -> FAIL (fdo#106641)
igt@kms_setmode@basic:
shard-apl: PASS -> FAIL (fdo#99912)
==== Possible fixes ====
igt@gem_ppgtt@blt-vs-render-ctxn:
shard-kbl: INCOMPLETE (fdo#106023, fdo#103665) -> PASS +1
igt@kms_flip@flip-vs-expired-vblank:
shard-glk: FAIL (fdo#105363) -> PASS
igt@kms_setmode@basic:
shard-kbl: FAIL (fdo#99912) -> PASS
fdo#103665 https://bugs.freedesktop.org/show_bug.cgi?id=103665
fdo#105363 https://bugs.freedesktop.org/show_bug.cgi?id=105363
fdo#106023 https://bugs.freedesktop.org/show_bug.cgi?id=106023
fdo#106641 https://bugs.freedesktop.org/show_bug.cgi?id=106641
fdo#99912 https://bugs.freedesktop.org/show_bug.cgi?id=99912
== Participating hosts (5 -> 5) ==
No changes in participating hosts
== Build changes ==
* Linux: CI_DRM_4695 -> Patchwork_9987
CI_DRM_4695: f352837700ec39dbaf00cdf727650851993d754b @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_4608: 94ebd21177feedf03e8f6dd1e73dca1a6ec7a0ac @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_9987: d9f67334c780e3eaedae58d8a87aaa8d3e3574b3 @ git://anongit.freedesktop.org/gfx-ci/linux
piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ git://anongit.freedesktop.org/piglit
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_9987/shards.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-08-22 10:09 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20180822085418epcas5p30ab8aa4b49ba204f4891760af002bce1@epcas5p3.samsung.com>
2018-08-22 8:54 ` [PATCH 1/4] fbdev: Drop FBINFO_CAN_FORCE_OUTPUT flag Daniel Vetter
2018-08-22 8:54 ` Daniel Vetter
2018-08-22 8:54 ` [PATCH 2/4] vt: Remove vc_panic_force_write Daniel Vetter
2018-08-22 8:59 ` Greg Kroah-Hartman
2018-08-22 8:59 ` Greg Kroah-Hartman
2018-09-11 12:11 ` Daniel Vetter
2018-08-22 8:54 ` [PATCH 3/4] fbdev: Add FBINFO_HIDE_SMEM_START flag Daniel Vetter
2018-08-22 8:54 ` Daniel Vetter
2018-08-22 8:54 ` Daniel Vetter
2018-09-03 16:48 ` Daniel Vetter
2018-09-03 16:48 ` Daniel Vetter
2018-09-03 16:48 ` Daniel Vetter
2018-09-10 12:51 ` Bartlomiej Zolnierkiewicz
2018-09-10 12:51 ` Bartlomiej Zolnierkiewicz
2018-08-22 8:54 ` [PATCH 4/4] drm/fb: Stop leaking physical address Daniel Vetter
2018-08-22 12:57 ` Sean Paul
2018-08-22 12:57 ` Sean Paul
2018-08-22 9:21 ` ✓ Fi.CI.BAT: success for series starting with [1/4] fbdev: Drop FBINFO_CAN_FORCE_OUTPUT flag Patchwork
2018-08-22 10:09 ` Patchwork [this message]
2018-09-10 12:48 ` [PATCH 1/4] " Bartlomiej Zolnierkiewicz
2018-09-10 12:48 ` Bartlomiej Zolnierkiewicz
2018-09-10 12:48 ` Bartlomiej Zolnierkiewicz
2018-09-11 7:42 ` Daniel Vetter
2018-09-11 7:42 ` Daniel Vetter
2018-09-11 7:42 ` Daniel Vetter
2018-09-11 8:47 ` Bartlomiej Zolnierkiewicz
2018-09-11 8:47 ` Bartlomiej Zolnierkiewicz
2018-09-11 8:47 ` Bartlomiej Zolnierkiewicz
2018-09-11 12:12 ` [Intel-gfx] " Daniel Vetter
2018-09-11 12:12 ` Daniel Vetter
2018-09-11 12:12 ` Daniel Vetter
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=20180822100936.30597.68075@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=daniel.vetter@ffwll.ch \
--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.