From: Patchwork <patchwork@emeril.freedesktop.org>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.BAT: warning for drm: Document code of conduct
Date: Tue, 11 Apr 2017 07:06:29 -0000 [thread overview]
Message-ID: <20170411070629.11628.97237@emeril.freedesktop.org> (raw)
In-Reply-To: <20170411064815.5399-1-daniel.vetter@ffwll.ch>
== Series Details ==
Series: drm: Document code of conduct
URL : https://patchwork.freedesktop.org/series/22830/
State : warning
== Summary ==
Series 22830v1 drm: Document code of conduct
https://patchwork.freedesktop.org/api/1.0/series/22830/revisions/1/mbox/
Test gem_exec_basic:
Subgroup basic-render:
pass -> DMESG-WARN (fi-snb-2520m)
Subgroup gtt-bsd:
pass -> DMESG-WARN (fi-snb-2520m)
pass -> DMESG-WARN (fi-snb-2600)
Subgroup gtt-default:
pass -> DMESG-WARN (fi-snb-2520m)
Subgroup gtt-render:
dmesg-warn -> PASS (fi-snb-2520m) fdo#100643
Subgroup readonly-blt:
pass -> DMESG-WARN (fi-snb-2520m)
Subgroup readonly-bsd:
dmesg-warn -> PASS (fi-snb-2520m) fdo#100643
Subgroup readonly-default:
dmesg-warn -> PASS (fi-snb-2520m) fdo#100643
Subgroup readonly-render:
dmesg-warn -> PASS (fi-snb-2600) fdo#100643
Test gem_exec_fence:
Subgroup basic-busy-default:
pass -> DMESG-WARN (fi-snb-2520m)
Subgroup basic-wait-default:
dmesg-warn -> PASS (fi-snb-2520m) fdo#100643
Test gem_exec_reloc:
Subgroup basic-cpu-active:
dmesg-warn -> PASS (fi-snb-2600) fdo#100643
Subgroup basic-gtt-active:
pass -> DMESG-WARN (fi-snb-2600)
Subgroup basic-gtt-read-active:
pass -> DMESG-WARN (fi-snb-2600)
Subgroup basic-write-cpu-active:
dmesg-warn -> PASS (fi-snb-2600) fdo#100643
Subgroup basic-write-read-active:
dmesg-warn -> PASS (fi-snb-2600) fdo#100643
Test gem_exec_store:
Subgroup basic-all:
pass -> DMESG-WARN (fi-snb-2600) fdo#100643
Subgroup basic-default:
dmesg-warn -> PASS (fi-snb-2600) fdo#100643
Test gem_exec_suspend:
Subgroup basic:
pass -> DMESG-WARN (fi-snb-2520m)
Subgroup basic-s4-devices:
dmesg-warn -> PASS (fi-kbl-7560u) fdo#100125
Test gem_mmap_gtt:
Subgroup basic-copy:
pass -> DMESG-WARN (fi-snb-2520m) fdo#100643
Subgroup basic-read:
dmesg-warn -> PASS (fi-snb-2520m) fdo#100643
Subgroup basic-read-no-prefault:
pass -> DMESG-WARN (fi-snb-2520m)
Subgroup basic-read-write:
dmesg-warn -> PASS (fi-snb-2520m) fdo#100643
Subgroup basic-short:
pass -> DMESG-WARN (fi-snb-2520m)
Subgroup basic-small-bo:
dmesg-warn -> PASS (fi-snb-2520m) fdo#100643
Test gem_ringfill:
Subgroup basic-default-fd:
pass -> DMESG-WARN (fi-snb-2520m)
Test kms_addfb_basic:
Subgroup basic:
pass -> DMESG-WARN (fi-snb-2600)
Subgroup basic-x-tiled:
dmesg-warn -> PASS (fi-snb-2600) fdo#100643
Subgroup framebuffer-vs-set-tiling:
pass -> DMESG-WARN (fi-snb-2600)
Subgroup invalid-get-prop:
dmesg-warn -> PASS (fi-snb-2600) fdo#100643
Subgroup size-max:
pass -> DMESG-WARN (fi-snb-2600)
Subgroup small-bo:
dmesg-warn -> PASS (fi-snb-2600) fdo#100643
Subgroup unused-modifier:
pass -> DMESG-WARN (fi-snb-2600)
Subgroup unused-offsets:
dmesg-warn -> PASS (fi-snb-2600) fdo#100643
Test kms_flip:
Subgroup basic-flip-vs-wf_vblank:
pass -> DMESG-WARN (fi-kbl-7560u)
Test kms_force_connector_basic:
Subgroup force-edid:
dmesg-warn -> PASS (fi-snb-2600) fdo#100643
Subgroup prune-stale-modes:
pass -> DMESG-WARN (fi-snb-2600) fdo#100643
Test kms_pipe_crc_basic:
Subgroup suspend-read-crc-pipe-c:
dmesg-warn -> PASS (fi-kbl-7560u) fdo#100445
Test kms_setmode:
Subgroup basic-clone-single-crtc:
pass -> DMESG-WARN (fi-snb-2600)
Test prime_vgem:
Subgroup basic-read:
pass -> DMESG-WARN (fi-snb-2520m)
Subgroup basic-sync-default:
dmesg-warn -> PASS (fi-snb-2520m) fdo#100643
WARNING: Long output truncated
e461ecfd413fb930d00f44f3de0019e528b4731f drm-tip: 2017y-04m-10d-14h-25m-24s UTC integration manifest
f254fbc drm: Document code of conduct
== Logs ==
For more details see: https://intel-gfx-ci.01.org/CI/Patchwork_4468/
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-04-11 7:06 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-11 6:48 [PATCH] drm: Document code of conduct Daniel Vetter
2017-04-11 7:06 ` Patchwork [this message]
2017-04-11 7:08 ` Daniel Stone
2017-04-11 7:33 ` Sumit Semwal
2017-04-11 7:51 ` Archit Taneja
2017-04-11 8:25 ` [Intel-gfx] " Martin Peres
2017-04-12 12:59 ` Sumit Semwal
2017-04-11 9:03 ` Daniel Vetter
2017-04-11 9:52 ` Neil Armstrong
2017-04-12 9:35 ` Laurent Pinchart
2017-04-11 9:09 ` Chris Wilson
2017-04-11 9:19 ` Thierry Reding
2017-04-11 9:24 ` Jani Nikula
2017-04-11 9:43 ` Vincent ABRIOU
2017-04-11 10:01 ` Maarten Lankhorst
2017-04-11 10:04 ` Brian Starkey
2017-04-11 12:37 ` Rob Clark
2017-04-11 13:12 ` Luc Verhaegen
2017-04-11 13:24 ` Daniel Vetter
2017-04-11 13:30 ` Luc Verhaegen
2017-04-11 13:36 ` Daniel Vetter
2017-04-11 13:39 ` Luc Verhaegen
2017-04-11 13:58 ` Jani Nikula
2017-04-11 15:14 ` Luc Verhaegen
2017-04-11 15:31 ` Daniel Vetter
2017-04-11 15:48 ` Alex Deucher
2017-04-11 13:35 ` David Herrmann
2017-04-11 13:48 ` Sean Paul
2017-04-11 15:40 ` Harry Wentland
2017-04-11 15:50 ` Alex Deucher
2017-04-11 16:09 ` Daniel Vetter
2017-04-11 17:17 ` Alex Deucher
2017-04-11 16:19 ` Eric Anholt
2017-04-11 17:28 ` Gustavo Padovan
2017-04-12 9:26 ` Michel Dänzer
2017-04-12 13:34 ` Keith Packard
2017-04-14 2:43 ` Gabriel Krisman Bertazi
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=20170411070629.11628.97237@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