From: shuang.he@intel.com
To: shuang.he@intel.com, ethan.gao@intel.com,
intel-gfx@lists.freedesktop.org, mika.kuoppala@linux.intel.com
Subject: Re: [PATCH] drm/i915: Don't bail out early on i915_handle_error
Date: 03 Feb 2015 05:42:20 -0800 [thread overview]
Message-ID: <898e4a$dcc6ja@FMSMGA003.fm.intel.com> (raw)
In-Reply-To: <1422966445-25695-1-git-send-email-mika.kuoppala@intel.com>
Tested-By: PRC QA PRTS (Patch Regression Test System Contact: shuang.he@intel.com)
Task id: 5702
-------------------------------------Summary-------------------------------------
Platform Delta drm-intel-nightly Series Applied
PNV 283/283 283/283
ILK -1 319/319 318/319
SNB +1-1 322/346 322/346
IVB +1-1 382/384 382/384
BYT 296/296 296/296
HSW +1 425/428 426/428
BDW -1 319/333 318/333
-------------------------------------Detailed-------------------------------------
Platform Test drm-intel-nightly Series Applied
ILK igt_gem_unfence_active_buffers DMESG_WARN(1, M37)PASS(3, M26) DMESG_WARN(1, M37)
*SNB igt_kms_flip_event_leak NSPT(7, M35M22) PASS(1, M35)
*SNB igt_kms_flip_single-buffer-flip-vs-dpms-off-vs-modeset PASS(2, M35) NSPT(1, M35)
*IVB igt_gem_pwrite_pread_snooped-copy-performance PASS(3, M34) DMESG_WARN(1, M34)
IVB igt_gem_pwrite_pread_snooped-pwrite-blt-cpu_mmap-performance DMESG_WARN(11, M34M21)PASS(10, M4M34) PASS(1, M34)
HSW igt_gem_pwrite_pread_snooped-pwrite-blt-cpu_mmap-performance DMESG_WARN(3, M40)PASS(24, M40M20) PASS(1, M40)
*BDW igt_gem_fence_thrash_bo-write-verify-threaded-none PASS(3, M30) DMESG_WARN(1, M30)
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
prev parent reply other threads:[~2015-02-03 13:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-03 12:27 [PATCH] drm/i915: Don't bail out early on i915_handle_error Mika Kuoppala
2015-02-03 12:29 ` Chris Wilson
2015-02-03 12:55 ` Jani Nikula
2015-02-03 13:42 ` shuang.he [this message]
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='898e4a$dcc6ja@FMSMGA003.fm.intel.com' \
--to=shuang.he@intel.com \
--cc=ethan.gao@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mika.kuoppala@linux.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