From: Patchwork <patchwork@emeril.freedesktop.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.BAT: warning for series starting with [1/5] drm/i915: Move intel_prepare_plane_fb() and intel_cleanup_plane_fb()
Date: Tue, 15 Nov 2016 09:15:50 -0000 [thread overview]
Message-ID: <20161115091550.9656.37213@emeril.freedesktop.org> (raw)
In-Reply-To: <20161115085817.4210-1-chris@chris-wilson.co.uk>
== Series Details ==
Series: series starting with [1/5] drm/i915: Move intel_prepare_plane_fb() and intel_cleanup_plane_fb()
URL : https://patchwork.freedesktop.org/series/15325/
State : warning
== Summary ==
Series 15325v1 Series without cover letter
https://patchwork.freedesktop.org/api/1.0/series/15325/revisions/1/mbox/
Test drv_module_reload_basic:
pass -> DMESG-WARN (fi-hsw-4770r)
pass -> DMESG-WARN (fi-skl-6700hq)
pass -> DMESG-WARN (fi-bsw-n3050)
pass -> DMESG-WARN (fi-skl-6770hq)
pass -> DMESG-WARN (fi-bdw-5557u)
pass -> DMESG-WARN (fi-ivb-3770)
pass -> DMESG-WARN (fi-skl-6260u)
pass -> DMESG-WARN (fi-ivb-3520m)
Test kms_pipe_crc_basic:
Subgroup hang-read-crc-pipe-a:
pass -> DMESG-WARN (fi-skl-6770hq)
Subgroup read-crc-pipe-b-frame-sequence:
pass -> DMESG-WARN (fi-skl-6770hq)
fi-bdw-5557u total:244 pass:228 dwarn:1 dfail:0 fail:0 skip:15
fi-bsw-n3050 total:244 pass:203 dwarn:1 dfail:0 fail:0 skip:40
fi-byt-j1900 total:244 pass:216 dwarn:0 dfail:0 fail:0 skip:28
fi-byt-n2820 total:244 pass:212 dwarn:0 dfail:0 fail:0 skip:32
fi-hsw-4770 total:244 pass:224 dwarn:0 dfail:0 fail:0 skip:20
fi-hsw-4770r total:244 pass:223 dwarn:1 dfail:0 fail:0 skip:20
fi-ilk-650 total:244 pass:191 dwarn:0 dfail:0 fail:0 skip:53
fi-ivb-3520m total:244 pass:221 dwarn:1 dfail:0 fail:0 skip:22
fi-ivb-3770 total:244 pass:221 dwarn:1 dfail:0 fail:0 skip:22
fi-kbl-7200u total:244 pass:222 dwarn:0 dfail:0 fail:0 skip:22
fi-skl-6260u total:244 pass:229 dwarn:1 dfail:0 fail:0 skip:14
fi-skl-6700hq total:244 pass:222 dwarn:1 dfail:0 fail:0 skip:21
fi-skl-6700k total:244 pass:222 dwarn:1 dfail:0 fail:0 skip:21
fi-skl-6770hq total:244 pass:227 dwarn:3 dfail:0 fail:0 skip:14
fi-snb-2520m total:244 pass:212 dwarn:0 dfail:0 fail:0 skip:32
fi-snb-2600 total:244 pass:211 dwarn:0 dfail:0 fail:0 skip:33
6cdc55e3a3822b1a0faff0124828816384bd04e1 drm-intel-nightly: 2016y-11m-15d-08h-13m-16s UTC integration manifest
c1e9b34 drm/i915: Set crtc_state->fb_changed whenever a VMA is changed
7a960c5 drm/i915: Quick spring clean of intel_prepare_plane_fb()
144db97 drm/i915: Track pinned vma in intel_plane_state
6e62480 drm/i915: Always prepare planes at the start of an atomic commit
34f16e2 drm/i915: Move intel_prepare_plane_fb() and intel_cleanup_plane_fb()
== Logs ==
For more details see: https://intel-gfx-ci.01.org/CI/Patchwork_2996/
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-11-15 9:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-15 8:58 [PATCH 1/5] drm/i915: Move intel_prepare_plane_fb() and intel_cleanup_plane_fb() Chris Wilson
2016-11-15 8:58 ` [PATCH 2/5] drm/i915: Always prepare planes at the start of an atomic commit Chris Wilson
2016-11-15 9:37 ` Daniel Vetter
2016-11-15 9:47 ` Tvrtko Ursulin
2016-11-15 9:57 ` Chris Wilson
2016-11-15 10:10 ` Daniel Vetter
2016-11-15 10:18 ` Chris Wilson
2016-11-15 8:58 ` [PATCH 3/5] drm/i915: Track pinned vma in intel_plane_state Chris Wilson
2016-11-15 9:52 ` Daniel Vetter
2016-11-15 10:02 ` Chris Wilson
2016-11-15 10:13 ` Daniel Vetter
2016-11-15 10:24 ` Daniel Vetter
2016-11-15 8:58 ` [PATCH 4/5] drm/i915: Quick spring clean of intel_prepare_plane_fb() Chris Wilson
2016-11-15 10:23 ` Daniel Vetter
2016-11-15 8:58 ` [PATCH 5/5] drm/i915: Set crtc_state->fb_changed whenever a VMA is changed Chris Wilson
2016-11-15 10:15 ` Daniel Vetter
2016-11-15 9:15 ` Patchwork [this message]
2016-11-15 9:28 ` [PATCH 1/5] drm/i915: Move intel_prepare_plane_fb() and intel_cleanup_plane_fb() 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=20161115091550.9656.37213@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=chris@chris-wilson.co.uk \
--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;
as well as URLs for NNTP newsgroup(s).