From: shuang.he@intel.com
To: shuang.he@intel.com, ethan.gao@intel.com,
intel-gfx@lists.freedesktop.org, rodrigo.vivi@intel.com
Subject: Re: [PATCH] drm/i915: PSR: Fix DP_PSR_NO_TRAIN_ON_EXIT logic
Date: 16 Mar 2015 16:36:13 -0700 [thread overview]
Message-ID: <2d8c1b$k9fg3v@fmsmga001.fm.intel.com> (raw)
In-Reply-To: <1426527344-2876-1-git-send-email-rodrigo.vivi@intel.com>
Tested-By: PRC QA PRTS (Patch Regression Test System Contact: shuang.he@intel.com)
Task id: 5962
-------------------------------------Summary-------------------------------------
Platform Delta drm-intel-nightly Series Applied
PNV 275/275 275/275
ILK 303/303 303/303
SNB -1 279/279 278/279
IVB 343/343 343/343
BYT 287/287 287/287
HSW 361/361 361/361
BDW 308/308 308/308
-------------------------------------Detailed-------------------------------------
Platform Test drm-intel-nightly Series Applied
*SNB igt_gem_persistent_relocs_forked-interruptible-thrash-inactive PASS(3) 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-03-16 23:36 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-28 1:26 [PATCH 1/7] drm/i915: PSR: Remove wrong LINK_DISABLE Rodrigo Vivi
2015-02-28 1:26 ` [PATCH 2/7] drm/i915: PSR: Fix DP_PSR_NO_TRAIN_ON_EXIT logic Rodrigo Vivi
2015-03-16 5:24 ` R, Durgadoss
2015-03-16 17:35 ` [PATCH] " Rodrigo Vivi
2015-03-16 23:36 ` shuang.he [this message]
2015-03-24 15:29 ` Rodrigo Vivi
2015-03-25 0:39 ` Runyan, Arthur J
2015-04-10 18:10 ` Rodrigo Vivi
2015-04-11 1:22 ` shuang.he
2015-04-14 13:18 ` R, Durgadoss
2015-02-28 1:26 ` [PATCH 3/7] drm/i915: PSR: deprecate link_standby support for core platforms Rodrigo Vivi
2015-03-02 11:41 ` Jindal, Sonika
2015-03-02 20:27 ` Rodrigo Vivi
2015-03-16 5:28 ` R, Durgadoss
2015-03-16 17:37 ` [PATCH] " Rodrigo Vivi
2015-03-16 17:38 ` Rodrigo Vivi
2015-02-28 1:26 ` [PATCH 4/7] drm/i915: PSR VLV: Add single frame update Rodrigo Vivi
2015-03-05 2:48 ` Pandiyan, Dhinakaran
2015-02-28 1:26 ` [PATCH 5/7] drm/i915: Make sure we invalidate frontbuffer on fbcon Rodrigo Vivi
2015-03-02 17:59 ` Daniel Vetter
2015-03-02 18:35 ` Vivi, Rodrigo
2015-03-03 8:28 ` Daniel Vetter
2015-03-03 20:03 ` Vivi, Rodrigo
2015-03-04 14:30 ` Daniel Vetter
2015-03-04 23:05 ` Rodrigo Vivi
2015-03-05 12:06 ` Daniel Vetter
2015-03-10 0:57 ` [PATCH] " Rodrigo Vivi
2015-03-10 10:08 ` shuang.he
2015-03-10 10:23 ` Daniel Vetter
2015-02-28 1:26 ` [PATCH 6/7] drm/i915: VLV/CHV PSR: Increase wait delay time before active PSR Rodrigo Vivi
2015-03-16 5:15 ` R, Durgadoss
2015-02-28 1:26 ` [PATCH 7/7] drm/i915: Enable PSR by default Rodrigo Vivi
2015-03-03 9:54 ` shuang.he
2015-03-16 5:31 ` R, Durgadoss
2015-03-23 20:20 ` Rodrigo Vivi
2015-03-24 10:03 ` Daniel Vetter
2015-03-24 10:08 ` Chris Wilson
2015-03-24 20:55 ` Vivi, Rodrigo
2015-03-24 22:05 ` chris
2015-03-25 13:53 ` Daniel Vetter
2015-03-25 19:27 ` Vivi, Rodrigo
2015-03-25 19:40 ` chris
2015-03-02 17:56 ` [PATCH 1/7] drm/i915: PSR: Remove wrong LINK_DISABLE Daniel Vetter
2015-03-16 5:15 ` R, Durgadoss
2015-04-09 17:42 ` Matthew Garrett
2015-04-13 23:11 ` Rodrigo Vivi
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='2d8c1b$k9fg3v@fmsmga001.fm.intel.com' \
--to=shuang.he@intel.com \
--cc=ethan.gao@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rodrigo.vivi@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