From: shuang.he@intel.com
To: shuang.he@intel.com, ethan.gao@intel.com,
intel-gfx@lists.freedesktop.org, sonika.jindal@intel.com
Subject: Re: [PATCH] drm: Adding edp1.4 specific dpcd macros
Date: 19 Feb 2015 02:31:58 -0800 [thread overview]
Message-ID: <898e4a$djhr8a@FMSMGA003.fm.intel.com> (raw)
In-Reply-To: <1424332004-6951-1-git-send-email-sonika.jindal@intel.com>
Tested-By: PRC QA PRTS (Patch Regression Test System Contact: shuang.he@intel.com)
Task id: 5793
-------------------------------------Summary-------------------------------------
Platform Delta drm-intel-nightly Series Applied
PNV -7 277/277 270/277
ILK 313/313 313/313
SNB 309/309 309/309
IVB 382/382 382/382
BYT 296/296 296/296
HSW 425/425 425/425
BDW -1 318/318 317/318
-------------------------------------Detailed-------------------------------------
Platform Test drm-intel-nightly Series Applied
*PNV igt_gem_evict_everything_minor-normal PASS(2) DMESG_WARN(1)PASS(1)
*PNV igt_gem_fence_thrash_bo-write-verify-none NRUN(1)PASS(5) FAIL(1)PASS(1)
*PNV igt_gem_fence_thrash_bo-write-verify-x PASS(6) FAIL(1)PASS(1)
*PNV igt_gem_fence_thrash_bo-write-verify-y NO_RESULT(1)PASS(5) FAIL(1)PASS(1)
*PNV igt_gem_set_tiling_vs_blt_tiled-to-tiled PASS(2) FAIL(1)PASS(1)
*PNV igt_gem_set_tiling_vs_blt_tiled-to-untiled PASS(3) FAIL(1)PASS(1)
PNV igt_gem_userptr_blits_coherency-sync NO_RESULT(1)CRASH(3)PASS(4) CRASH(2)
*BDW igt_gem_gtt_hog PASS(11) DMESG_WARN(1)PASS(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
next prev parent reply other threads:[~2015-02-19 10:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-19 7:46 [PATCH] drm: Adding edp1.4 specific dpcd macros Sonika Jindal
2015-02-19 10:31 ` shuang.he [this message]
2015-02-19 17:46 ` Todd Previte
2015-02-20 8:25 ` Jani Nikula
2015-02-20 17:00 ` Todd Previte
2015-02-23 23:51 ` 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='898e4a$djhr8a@FMSMGA003.fm.intel.com' \
--to=shuang.he@intel.com \
--cc=ethan.gao@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=sonika.jindal@intel.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