From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Souza, Jose" <jose.souza@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✓ Fi.CI.BAT: success for series starting with [v3,1/2] drm/i915: Add HAS_DISPLAY() and use it (rev2)
Date: Tue, 04 Dec 2018 08:38:46 -0000 [thread overview]
Message-ID: <20181204083846.4005.20784@emeril.freedesktop.org> (raw)
In-Reply-To: <20181130232048.14216-1-jose.souza@intel.com>
== Series Details ==
Series: series starting with [v3,1/2] drm/i915: Add HAS_DISPLAY() and use it (rev2)
URL : https://patchwork.freedesktop.org/series/53341/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5247 -> Patchwork_11002
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://patchwork.freedesktop.org/api/1.0/series/53341/revisions/2/mbox/
Known issues
------------
Here are the changes found in Patchwork_11002 that come from known issues:
### IGT changes ###
#### Possible fixes ####
* igt@gem_ctx_create@basic-files:
- fi-bsw-n3050: FAIL [fdo#108656] -> PASS
* igt@gem_exec_suspend@basic-s3:
- fi-cfl-8109u: DMESG-WARN [fdo#107345] -> PASS +3
* igt@i915_selftest@live_evict:
- fi-bsw-kefka: DMESG-WARN [fdo#107709] -> PASS
[fdo#107345]: https://bugs.freedesktop.org/show_bug.cgi?id=107345
[fdo#107709]: https://bugs.freedesktop.org/show_bug.cgi?id=107709
[fdo#108656]: https://bugs.freedesktop.org/show_bug.cgi?id=108656
Participating hosts (48 -> 42)
------------------------------
Missing (6): fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-skl-6260u fi-ctg-p8600
Build changes
-------------
* Linux: CI_DRM_5247 -> Patchwork_11002
CI_DRM_5247: ff3d336ae5b3ef75e12ed400fd4ccb55701c212a @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_4736: 285ebfb3b7adc56586031afa5150c4e5ad40c229 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_11002: b7a8a1adc388f6c90053f40a3538b9c599a7480f @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
b7a8a1adc388 drm/i915: Move display device info capabilities to its own struct
2ea25bb8bc83 drm/i915: Add HAS_DISPLAY() and use it
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_11002/
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-12-04 8:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-30 23:20 [PATCH v3 1/2] drm/i915: Add HAS_DISPLAY() and use it José Roberto de Souza
2018-11-30 23:20 ` [PATCH v3 2/2] drm/i915: Move display device info capabilities to its own struct José Roberto de Souza
2018-11-30 23:32 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [v3,1/2] drm/i915: Add HAS_DISPLAY() and use it Patchwork
2018-11-30 23:34 ` ✗ Fi.CI.SPARSE: " Patchwork
2018-11-30 23:52 ` ✓ Fi.CI.BAT: success " Patchwork
2018-12-01 18:32 ` ✗ Fi.CI.IGT: failure " Patchwork
2018-12-03 23:00 ` Souza, Jose
2018-12-03 18:21 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [v3,1/2] drm/i915: Add HAS_DISPLAY() and use it (rev2) Patchwork
2018-12-03 18:23 ` ✗ Fi.CI.SPARSE: " Patchwork
2018-12-04 8:38 ` Patchwork [this message]
2018-12-04 10:34 ` ✓ 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=20181204083846.4005.20784@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jose.souza@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;
as well as URLs for NNTP newsgroup(s).