From: shuang.he@intel.com
To: shuang.he@intel.com, ethan.gao@intel.com,
intel-gfx@lists.freedesktop.org, jbarnes@virtuousgeek.org
Subject: Re: [PATCH] drm/i915: list self-refresh as enabled on newer platforms
Date: 02 Apr 2015 22:21:22 -0700 [thread overview]
Message-ID: <acb6cf$ku4ohs@fmsmga002.fm.intel.com> (raw)
In-Reply-To: <1427998729-30794-1-git-send-email-jbarnes@virtuousgeek.org>
Tested-By: Intel Graphics QA PRTS (Patch Regression Test System Contact: shuang.he@intel.com)
Task id: 6125
-------------------------------------Summary-------------------------------------
Platform Delta drm-intel-nightly Series Applied
PNV -3 272/272 269/272
ILK 302/302 302/302
SNB 303/303 303/303
IVB 338/338 338/338
BYT -1 287/287 286/287
HSW 361/361 361/361
BDW 308/308 308/308
-------------------------------------Detailed-------------------------------------
Platform Test drm-intel-nightly Series Applied
PNV igt@gem_tiled_pread_pwrite FAIL(3)PASS(10) FAIL(1)PASS(1)
PNV igt@gem_userptr_blits@coherency-sync CRASH(5)PASS(7) CRASH(1)PASS(1)
PNV igt@gen3_render_tiledx_blits FAIL(6)PASS(5) FAIL(1)PASS(1)
*BYT igt@gem_exec_bad_domains@conflicting-write-domain PASS(17) FAIL(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
prev parent reply other threads:[~2015-04-03 5:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-02 18:18 [PATCH] drm/i915: list self-refresh as enabled on newer platforms Jesse Barnes
2015-04-02 18:42 ` Ville Syrjälä
2015-04-02 18:48 ` Jesse Barnes
2015-05-27 7:05 ` [PATCH] drm/i915: Include VLV in self refresh status Ander Conselvan de Oliveira
2015-06-02 11:17 ` [PATCH] drm/i915: Include G4X/VLV/CHV " Ander Conselvan de Oliveira
2015-06-02 11:51 ` Ville Syrjälä
2015-06-02 11:58 ` Jani Nikula
2015-06-04 8:23 ` Jani Nikula
2015-06-02 17:46 ` shuang.he
2015-04-03 5:21 ` 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$ku4ohs@fmsmga002.fm.intel.com' \
--to=shuang.he@intel.com \
--cc=ethan.gao@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jbarnes@virtuousgeek.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.