From: shuang.he@intel.com
To: shuang.he@intel.com, lei.a.liu@intel.com,
intel-gfx@lists.freedesktop.org, tprevite@gmail.com
Subject: Re: [PATCH 3/3] drm/i915: Displayport compliance test 4.2.2.8 support
Date: 28 Jun 2015 10:15:23 -0700 [thread overview]
Message-ID: <acb6cf$md69s0@fmsmga002.fm.intel.com> (raw)
In-Reply-To: <1433895740-13698-4-git-send-email-tprevite@gmail.com>
Tested-By: Intel Graphics QA PRTS (Patch Regression Test System Contact: shuang.he@intel.com)
Task id: 6621
-------------------------------------Summary-------------------------------------
Platform Delta drm-intel-nightly Series Applied
ILK 302/302 302/302
SNB 312/316 312/316
IVB 343/343 343/343
BYT -2 287/287 285/287
HSW 380/380 380/380
-------------------------------------Detailed-------------------------------------
Platform Test drm-intel-nightly Series Applied
*BYT igt@gem_partial_pwrite_pread@reads-display PASS(1) FAIL(1)
*BYT igt@gem_partial_pwrite_pread@reads-uncached PASS(1) FAIL(1)
Note: You need to pay more attention to line start with '*'
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2015-06-28 17:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-10 0:22 Add support for Displayport CTS 4.2.2.7, 4.2.2.8 and 4.2.2.9 Todd Previte
2015-06-10 0:22 ` [PATCH 1/3] drm/i915: Displayport compliance test 4.2.2.9 support Todd Previte
2015-06-15 15:37 ` Daniel Vetter
2015-06-15 15:50 ` Chris Wilson
2015-06-10 0:22 ` [PATCH 2/3] drm/i915: Displayport compliance test 4.2.2.7 support Todd Previte
2015-06-15 15:39 ` Daniel Vetter
2015-06-10 0:22 ` [PATCH 3/3] drm/i915: Displayport compliance test 4.2.2.8 support Todd Previte
2015-06-15 15:42 ` Daniel Vetter
2015-06-28 17:15 ` shuang.he [this message]
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='acb6cf$md69s0@fmsmga002.fm.intel.com' \
--to=shuang.he@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lei.a.liu@intel.com \
--cc=tprevite@gmail.com \
/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