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: Handle inaccurate time conversion
Date: 28 Nov 2014 11:09:40 -0800 [thread overview]
Message-ID: <dbd59e$j21d5d@fmsmga002.fm.intel.com> (raw)
In-Reply-To: <1417166995-10803-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_reloc_overflow_source-offset-big-reloc-gtt PASS(2, M25) NO_RESULT(1, M25)
*PNV igt_gem_ringfill_blitter PASS(2, M25) NO_RESULT(1, M25)
ILK igt_kms_flip_wf_vblank-ts-check DMESG_WARN(2, M26)PASS(4, 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-11-28 19:10 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-28 9:29 [PATCH 1/2] drm/i915: compute wait_ioctl timeout correctly Daniel Vetter
2014-11-28 9:29 ` [PATCH 2/2] drm/i915: Handle inaccurate time conversion issues Daniel Vetter
2014-11-28 11:08 ` Chris Wilson
2014-11-28 13:30 ` Daniel Vetter
2014-11-28 12:13 ` Chris Wilson
2014-11-28 19:09 ` shuang.he [this message]
2014-12-08 12:34 ` Jani Nikula
2014-11-28 10:09 ` [PATCH 1/2] drm/i915: compute wait_ioctl timeout correctly Chris Wilson
2014-11-28 13:46 ` Dave Gordon
2014-12-02 14:56 ` Daniel Vetter
2014-12-02 15:22 ` [PATCH] " Daniel Vetter
2014-12-02 15:22 ` Daniel Vetter
2014-12-02 15:36 ` Daniel Vetter
2014-12-02 15:36 ` Daniel Vetter
2014-12-02 16:35 ` [Intel-gfx] " Chris Wilson
2014-12-02 16:35 ` Chris Wilson
2014-12-02 16:54 ` [Intel-gfx] " John Stultz
2014-12-03 9:22 ` Daniel Vetter
2014-12-03 9:22 ` Daniel Vetter
2014-12-03 10:28 ` [Intel-gfx] " Imre Deak
2014-12-03 10:28 ` Imre Deak
2014-12-03 14:30 ` [Intel-gfx] " Daniel Vetter
2014-12-03 14:30 ` Daniel Vetter
2014-12-03 19:07 ` [Intel-gfx] " John Stultz
2014-12-03 19:07 ` John Stultz
2014-12-04 10:42 ` [Intel-gfx] " Daniel Vetter
2014-12-04 10:42 ` Daniel Vetter
2014-12-04 17:42 ` [Intel-gfx] " John Stultz
2014-12-04 17:42 ` John Stultz
2014-12-04 17:50 ` [Intel-gfx] " Daniel Vetter
2014-12-04 17:50 ` Daniel Vetter
2014-12-04 18:16 ` [Intel-gfx] " John Stultz
2014-12-04 18:16 ` John Stultz
2014-12-04 18:51 ` [Intel-gfx] " Daniel Vetter
2014-12-04 18:51 ` Daniel Vetter
2014-12-04 20:35 ` [Intel-gfx] " John Stultz
2014-12-04 20:35 ` John Stultz
2014-12-05 9:16 ` [Intel-gfx] " Daniel Vetter
2014-12-05 9:16 ` Daniel Vetter
2014-12-03 5:21 ` shuang.he
2014-12-03 5:51 ` shuang.he
2014-12-04 10:12 ` Daniel Vetter
2014-12-04 10:12 ` Daniel Vetter
2014-12-04 17:03 ` shuang.he
2014-12-04 17:45 ` John Stultz
2014-12-04 17:45 ` John Stultz
2014-12-08 12:34 ` [Intel-gfx] " Jani Nikula
2014-12-08 12:34 ` 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='dbd59e$j21d5d@fmsmga002.fm.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 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.