From: shuang.he@intel.com
To: shuang.he@intel.com, ethan.gao@intel.com,
intel-gfx@lists.freedesktop.org, imre.deak@intel.com
Subject: Re: [PATCH] drm/i915: avoid processing spurious/shared interrupts in low-power states
Date: 20 Feb 2015 14:26:51 -0800 [thread overview]
Message-ID: <84c8a8$jglnlp@orsmga001.jf.intel.com> (raw)
In-Reply-To: <1424459342-25642-1-git-send-email-imre.deak@intel.com>
Tested-By: PRC QA PRTS (Patch Regression Test System Contact: shuang.he@intel.com)
Task id: 5801
-------------------------------------Summary-------------------------------------
Platform Delta drm-intel-nightly Series Applied
PNV 277/277 277/277
ILK -1 313/313 312/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
*ILK igt_gem_unfence_active_buffers PASS(2) DMESG_WARN(1)PASS(1)
*BDW igt_gem_gtt_hog PASS(18) 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-20 22:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-20 19:09 [PATCH] drm/i915: avoid processing spurious/shared interrupts in low-power states Imre Deak
2015-02-20 19:40 ` Chris Wilson
2015-02-20 19:53 ` Imre Deak
2015-02-20 22:26 ` shuang.he [this message]
2015-02-23 9:58 ` [PATCH v2] " Imre Deak
2015-02-23 11:57 ` Chris Wilson
2015-02-23 14:26 ` shuang.he
2015-02-23 14:31 ` [PATCH v3] " Imre Deak
2015-02-24 0:07 ` Daniel Vetter
2015-02-24 13:56 ` shuang.he
2015-02-24 9:14 ` [PATCH v4] " Imre Deak
2015-02-24 9:29 ` Chris Wilson
2015-02-24 10:42 ` Daniel Vetter
2015-02-24 11:00 ` Chris Wilson
2015-02-24 14:00 ` Jani Nikula
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='84c8a8$jglnlp@orsmga001.jf.intel.com' \
--to=shuang.he@intel.com \
--cc=ethan.gao@intel.com \
--cc=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox