From: Patchwork <patchwork@annarchy.freedesktop.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✓ Fi.CI.BAT: success for drm/i915: Reject invalid-pad for context-destroy and -create ioctls
Date: Mon, 08 Feb 2016 12:57:44 -0000 [thread overview]
Message-ID: <20160208125744.11236.59069@annarchy.freedesktop.org> (raw)
In-Reply-To: <1454690759-31201-1-git-send-email-chris@chris-wilson.co.uk>
== Summary ==
Series 3128v1 drm/i915: Reject invalid-pad for context-destroy and -create ioctls
http://patchwork.freedesktop.org/api/1.0/series/3128/revisions/1/mbox/
Test kms_force_connector_basic:
Subgroup force-edid:
skip -> PASS (snb-x220t)
bdw-nuci7 total:161 pass:152 dwarn:0 dfail:0 fail:0 skip:9
bdw-ultra total:164 pass:152 dwarn:0 dfail:0 fail:0 skip:12
bsw-nuc-2 total:164 pass:136 dwarn:0 dfail:0 fail:0 skip:28
byt-nuc total:164 pass:141 dwarn:0 dfail:0 fail:0 skip:23
hsw-brixbox total:164 pass:151 dwarn:0 dfail:0 fail:0 skip:13
hsw-gt2 total:164 pass:154 dwarn:0 dfail:0 fail:0 skip:10
ivb-t430s total:164 pass:150 dwarn:0 dfail:0 fail:0 skip:14
snb-dellxps total:164 pass:142 dwarn:0 dfail:0 fail:0 skip:22
snb-x220t total:164 pass:142 dwarn:0 dfail:0 fail:1 skip:21
Results at /archive/results/CI_IGT_test/Patchwork_1372/
4d509d986f45cef06e2683923e88ae568700ed23 drm-intel-nightly: 2016y-02m-05d-21h-37m-20s UTC integration manifest
bbd2b38f50cdf4d98297a8cea395615c17e5b67c drm/i915: Reject invalid-pad for context-destroy and -create ioctls
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-02-08 12:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-05 16:45 [PATCH v2] drm/i915: Reject invalid-pad for context-destroy and -create ioctls Chris Wilson
2016-02-08 12:55 ` ✓ Fi.CI.BAT: success for " Patchwork
2016-02-08 12:57 ` Patchwork [this message]
2016-02-15 17:02 ` [PATCH v2] " 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=20160208125744.11236.59069@annarchy.freedesktop.org \
--to=patchwork@annarchy.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).