From: shuang.he@intel.com
To: shuang.he@intel.com, ethan.gao@intel.com,
intel-gfx@lists.freedesktop.org, daniel.vetter@ffwll.ch
Subject: Re: [PATCH] drm: Fix deadlock due to getconnector locking changes
Date: 22 Feb 2015 05:55:45 -0800 [thread overview]
Message-ID: <71e320$fqe87b@orsmga003.jf.intel.com> (raw)
In-Reply-To: <1424601516-19267-1-git-send-email-daniel.vetter@ffwll.ch>
Tested-By: PRC QA PRTS (Patch Regression Test System Contact: shuang.he@intel.com)
Task id: 5803
-------------------------------------Summary-------------------------------------
Platform Delta drm-intel-nightly Series Applied
PNV -5 277/277 272/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_userptr_blits_coherency-sync NO_RESULT(1)CRASH(7)NRUN(1)PASS(6) CRASH(2)
PNV igt_gem_userptr_blits_coherency-unsync CRASH(5)NRUN(1)PASS(4) CRASH(1)NRUN(1)
*PNV igt_gem_userptr_blits_create-destroy-sync PASS(4) NRUN(1)PASS(1)
*PNV igt_gem_userptr_blits_dmabuf-sync PASS(3) NRUN(1)PASS(1)
*PNV igt_gem_userptr_blits_forked-sync-interruptible PASS(3) NRUN(1)PASS(1)
*BDW igt_gem_gtt_hog PASS(20) 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-22 14:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-22 10:38 [PATCH] drm: Fix deadlock due to getconnector locking changes Daniel Vetter
2015-02-22 13:55 ` shuang.he [this message]
2015-02-23 8:52 ` Jani Nikula
2015-02-23 12:28 ` Rob Clark
2015-02-23 23:55 ` Marc Finet
2015-03-02 20:03 ` Tommi Rantala
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='71e320$fqe87b@orsmga003.jf.intel.com' \
--to=shuang.he@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=ethan.gao@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