All of lore.kernel.org
 help / color / mirror / Atom feed
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/i915: Add module param to test the load detect code
Date: 04 Mar 2015 06:29:51 -0800	[thread overview]
Message-ID: <2d8c1b$k3ohgr@fmsmga001.fm.intel.com> (raw)
In-Reply-To: <1425402227-13557-1-git-send-email-daniel.vetter@ffwll.ch>

Tested-By: PRC QA PRTS (Patch Regression Test System Contact: shuang.he@intel.com)
Task id: 5880
-------------------------------------Summary-------------------------------------
Platform          Delta          drm-intel-nightly          Series Applied
PNV                 -2              278/278              276/278
ILK                                  308/308              308/308
SNB                                  284/284              284/284
IVB                                  380/380              380/380
BYT                                  294/294              294/294
HSW                                  387/387              387/387
BDW                 -1              316/316              315/316
-------------------------------------Detailed-------------------------------------
Platform  Test                                drm-intel-nightly          Series Applied
 PNV  igt_gem_userptr_blits_coherency-sync      NO_RESULT(1)CRASH(8)NRUN(1)PASS(8)      CRASH(1)PASS(1)
 PNV  igt_gem_userptr_blits_coherency-unsync      FAIL(1)NO_RESULT(1)CRASH(6)PASS(7)      CRASH(1)PASS(1)
*BDW  igt_gem_gtt_hog      PASS(19)      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

  parent reply	other threads:[~2015-03-04 14:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-03 17:03 [PATCH] drm/i915: Add module param to test the load detect code Daniel Vetter
2015-03-03 19:23 ` Jesse Barnes
2015-03-03 21:15   ` Chris Wilson
2015-03-04  0:06     ` Daniel Vetter
2015-03-04  0:27       ` Jesse Barnes
2015-03-04  8:56         ` Chris Wilson
2015-03-04 16:09           ` Jesse Barnes
2015-03-04 16:09         ` Daniel Vetter
2015-03-04 14:29 ` shuang.he [this message]
2015-03-27  9:57 ` Ander Conselvan De Oliveira

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$k3ohgr@fmsmga001.fm.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 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.