From: shuang.he@intel.com
To: shuang.he@intel.com, intel-gfx@lists.freedesktop.org,
daniel.vetter@ffwll.ch
Subject: Re: [PATCH 2/2] drm/i915: Don't capture pinned bo separately
Date: 02 Dec 2014 17:34:44 -0800 [thread overview]
Message-ID: <71e320$elqe9a@orsmga003.jf.intel.com> (raw)
In-Reply-To: <1417533584-2011-2-git-send-email-daniel.vetter@ffwll.ch>
Tested-By: PRC QA PRTS (Patch Regression Test System Contact: shuang.he@intel.com)
-------------------------------------Summary-------------------------------------
Platform Delta drm-intel-nightly Series Applied
PNV -2 364/364 362/364
ILK +1 365/366 366/366
SNB 450/450 450/450
IVB 498/498 498/498
BYT 289/289 289/289
HSW 564/564 564/564
BDW 417/417 417/417
-------------------------------------Detailed-------------------------------------
Platform Test drm-intel-nightly Series Applied
*PNV igt_gem_fence_thrash_bo-write-verify-x PASS(2, M25M23) NO_RESULT(1, M23)
*PNV igt_gem_tiled_partial_pwrite_pread_writes-after-reads PASS(2, M25M23) NO_RESULT(1, M23)
ILK igt_kms_flip_wf_vblank-ts-check DMESG_WARN(2, M26)PASS(11, M26M37) PASS(1, M37)
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:[~2014-12-03 1:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-02 15:19 [PATCH 1/2] drm/i915: Clean up pinned bo capture Daniel Vetter
2014-12-02 15:19 ` [PATCH 2/2] drm/i915: Don't capture pinned bo separately Daniel Vetter
2014-12-03 1:34 ` shuang.he [this message]
2014-12-02 16:46 ` [PATCH 1/2] drm/i915: Clean up pinned bo capture Chris Wilson
2014-12-03 14:16 ` Daniel Vetter
2014-12-04 9:11 ` Chris Wilson
2014-12-04 10:47 ` Daniel Vetter
-- strict thread matches above, loose matches on Subject: below --
2014-12-02 9:56 Daniel Vetter
2014-12-02 9:56 ` [PATCH 2/2] drm/i915: Don't capture pinned bo separately 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='71e320$elqe9a@orsmga003.jf.intel.com' \
--to=shuang.he@intel.com \
--cc=daniel.vetter@ffwll.ch \
--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