From: shuang.he@intel.com
To: shuang.he@intel.com, ethan.gao@intel.com,
intel-gfx@lists.freedesktop.org, matthew.d.roper@intel.com
Subject: Re: [PATCH] drm/i915: Don't clobber plane state on internal disables
Date: 04 Mar 2015 19:57:29 -0800 [thread overview]
Message-ID: <6299f3$km0peo@orsmga002.jf.intel.com> (raw)
In-Reply-To: <1425494944-15403-1-git-send-email-matthew.d.roper@intel.com>
Tested-By: PRC QA PRTS (Patch Regression Test System Contact: shuang.he@intel.com)
Task id: 5887
-------------------------------------Summary-------------------------------------
Platform Delta drm-intel-nightly Series Applied
PNV 280/280 280/280
ILK 308/308 308/308
SNB -1 328/328 327/328
IVB -1 379/379 378/379
BYT 294/294 294/294
HSW 387/387 387/387
BDW -1 316/316 315/316
-------------------------------------Detailed-------------------------------------
Platform Test drm-intel-nightly Series Applied
SNB igt_kms_rotation_crc_sprite-rotation DMESG_WARN(1)PASS(4) DMESG_WARN(2)
*IVB igt_kms_rotation_crc_sprite-rotation PASS(2) DMESG_WARN(2)
*BDW igt_gem_gtt_hog 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-05 3:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-04 18:49 [PATCH] drm/i915: Don't clobber plane state on internal disables Matt Roper
2015-03-04 18:50 ` [PATCH i-g-t] tests/kms_plane: Ensure planes recover from DPMS Matt Roper
2015-03-05 12:32 ` Daniel Vetter
2015-03-05 15:01 ` Matt Roper
2015-03-06 16:55 ` Daniel Vetter
2015-03-05 3:57 ` shuang.he [this message]
2015-03-05 12:33 ` [PATCH] drm/i915: Don't clobber plane state on internal disables 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='6299f3$km0peo@orsmga002.jf.intel.com' \
--to=shuang.he@intel.com \
--cc=ethan.gao@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.d.roper@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 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.