From: Patchwork <patchwork@emeril.freedesktop.org>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✓ Fi.CI.BAT: success for drivers/base: use a worker for sysfs unbind (rev3)
Date: Sun, 09 Dec 2018 22:27:18 -0000 [thread overview]
Message-ID: <20181209222718.11921.80094@emeril.freedesktop.org> (raw)
In-Reply-To: <20181207093133.15648-1-daniel.vetter@ffwll.ch>
== Series Details ==
Series: drivers/base: use a worker for sysfs unbind (rev3)
URL : https://patchwork.freedesktop.org/series/53734/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5291 -> Patchwork_11054
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://patchwork.freedesktop.org/api/1.0/series/53734/revisions/3/mbox/
Known issues
------------
Here are the changes found in Patchwork_11054 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_ctx_create@basic-files:
- fi-bsw-n3050: PASS -> FAIL [fdo#108656]
- fi-bsw-kefka: PASS -> FAIL [fdo#108656]
* igt@i915_selftest@live_execlists:
- fi-apl-guc: PASS -> INCOMPLETE [fdo#103927] / [fdo#108622]
#### Possible fixes ####
* igt@gem_exec_suspend@basic-s4-devices:
- fi-ivb-3520m: FAIL [fdo#108880] -> PASS
[fdo#103927]: https://bugs.freedesktop.org/show_bug.cgi?id=103927
[fdo#108622]: https://bugs.freedesktop.org/show_bug.cgi?id=108622
[fdo#108656]: https://bugs.freedesktop.org/show_bug.cgi?id=108656
[fdo#108880]: https://bugs.freedesktop.org/show_bug.cgi?id=108880
Participating hosts (51 -> 43)
------------------------------
Missing (8): fi-kbl-soraka fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-ctg-p8600 fi-pnv-d510 fi-kbl-7560u
Build changes
-------------
* Linux: CI_DRM_5291 -> Patchwork_11054
CI_DRM_5291: 9bb72982ee481a5ae4da600e270d87c8416525a7 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_4743: edb2db2cf2b6665d7ba3fa9117263302f6307a4f @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_11054: e6e8351e1d29ef97ac018b821e7c4bb9327e9ca5 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
e6e8351e1d29 drivers/base: use a worker for sysfs unbind
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_11054/
_______________________________________________
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-09 22:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-07 9:31 [PATCH] drivers/base: use a worker for sysfs unbind Daniel Vetter
2018-12-07 9:58 ` Chris Wilson
2018-12-07 11:00 ` Daniel Vetter
2018-12-07 11:51 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2018-12-07 12:15 ` ✗ Fi.CI.BAT: failure " Patchwork
2018-12-07 12:24 ` Chris Wilson
2018-12-07 16:01 ` [PATCH] " Daniel Vetter
2018-12-09 17:20 ` Daniel Vetter
2018-12-13 9:39 ` Chris Wilson
2018-12-07 17:12 ` ✗ Fi.CI.CHECKPATCH: warning for drivers/base: use a worker for sysfs unbind (rev2) Patchwork
2018-12-07 17:36 ` ✗ Fi.CI.BAT: failure " Patchwork
2018-12-09 22:05 ` ✗ Fi.CI.CHECKPATCH: warning for drivers/base: use a worker for sysfs unbind (rev3) Patchwork
2018-12-09 22:27 ` Patchwork [this message]
2018-12-09 23: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=20181209222718.11921.80094@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox