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 RESEND: dma-buf cleanup
Date: Wed, 04 Jul 2018 10:08:30 -0000 [thread overview]
Message-ID: <20180704100830.6641.15909@emeril.freedesktop.org> (raw)
In-Reply-To: <20180704092909.6599-1-daniel.vetter@ffwll.ch>
== Series Details ==
Series: RESEND: dma-buf cleanup
URL : https://patchwork.freedesktop.org/series/45890/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_4425 -> Patchwork_9520 =
== Summary - SUCCESS ==
No regressions found.
External URL: https://patchwork.freedesktop.org/api/1.0/series/45890/revisions/1/mbox/
== Known issues ==
Here are the changes found in Patchwork_9520 that come from known issues:
=== IGT changes ===
==== Possible fixes ====
igt@kms_pipe_crc_basic@suspend-read-crc-pipe-c:
fi-bxt-dsi: INCOMPLETE (fdo#103927) -> PASS
fdo#103927 https://bugs.freedesktop.org/show_bug.cgi?id=103927
== Participating hosts (46 -> 41) ==
Missing (5): fi-ctg-p8600 fi-ilk-m540 fi-byt-squawks fi-bsw-cyan fi-hsw-4200u
== Build changes ==
* Linux: CI_DRM_4425 -> Patchwork_9520
CI_DRM_4425: 655f2c563a64861ef52008d968092a62644caf96 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_4534: aeb3f4143572b81a907921ad9442858aafe1931e @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_9520: 8c7adfdbb9b6239efac49d24cb88a15f0b9cf1d4 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
8c7adfdbb9b6 dma-fence: Polish kernel-doc for dma-fence.c
ec7d80472d56 drm/vgem: Remove unecessary dma_fence_ops
6ab47e6389fa drm/nouveau: Remove unecessary dma_fence_ops
d134ee0947b1 drm/msm: Remove unecessary dma_fence_ops
80713ee8fc35 drm/i915: Remove unecessary dma_fence_ops
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_9520/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-07-04 10:08 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-04 9:29 [PATCH 0/5] RESEND: dma-buf cleanup Daniel Vetter
2018-07-04 9:29 ` [PATCH 1/5] drm/i915: Remove unecessary dma_fence_ops Daniel Vetter
2018-07-04 12:03 ` Emil Velikov
2018-07-04 12:34 ` Daniel Vetter
2018-07-04 17:22 ` Emil Velikov
2018-07-04 20:03 ` Daniel Vetter
[not found] ` <20180704092909.6599-1-daniel.vetter-/w4YWyX8dFk@public.gmane.org>
2018-07-04 9:29 ` [PATCH 2/5] drm/msm: " Daniel Vetter
2018-07-04 9:29 ` [PATCH 3/5] drm/nouveau: " Daniel Vetter
2018-07-04 9:29 ` [PATCH 4/5] drm/vgem: " Daniel Vetter
2018-08-09 8:33 ` Daniel Vetter
2018-08-09 8:38 ` Chris Wilson
2018-08-09 12:45 ` [PATCH] " Daniel Vetter
2018-08-09 12:48 ` Chris Wilson
2018-08-17 9:23 ` Daniel Vetter
2018-07-04 9:29 ` [PATCH 5/5] dma-fence: Polish kernel-doc for dma-fence.c Daniel Vetter
2018-07-04 9:29 ` Daniel Vetter
2018-07-04 9:36 ` Christian König
2018-07-04 9:36 ` Christian König
2018-07-04 9:53 ` ✗ Fi.CI.CHECKPATCH: warning for RESEND: dma-buf cleanup Patchwork
2018-07-04 10:08 ` Patchwork [this message]
2018-07-04 11:27 ` ✓ Fi.CI.IGT: success " Patchwork
2018-08-09 14:21 ` ✗ Fi.CI.CHECKPATCH: warning for RESEND: dma-buf cleanup (rev2) 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=20180704100830.6641.15909@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.