From: shuang.he@intel.com
To: shuang.he@intel.com, intel-gfx@lists.freedesktop.org,
daniel.vetter@ffwll.ch
Subject: Re: [PATCH] drm: Handle atomic state properly in kms getfoo
Date: 26 Nov 2014 05:00:32 -0800 [thread overview]
Message-ID: <bf3aaa$indr0u@fmsmga001.fm.intel.com> (raw)
In-Reply-To: <1416955805-31832-1-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 366/366 366/366
ILK -13 371/371 358/371
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
ILK igt_gem_reset_stats_close-pending-fork-render TIMEOUT(21, M37M26)PASS(1, M26) TIMEOUT(1, M26)
ILK igt_kms_flip_nonexisting-fb DMESG_WARN(3, M26)PASS(5, M37M26) DMESG_WARN(1, M26)
*ILK igt_kms_pipe_crc_basic_bad-nb-words-1 PASS(3, M37M26) DMESG_WARN(1, M26)
*ILK igt_kms_pipe_crc_basic_bad-pipe PASS(4, M37M26) DMESG_WARN(1, M26)
*ILK igt_kms_pipe_crc_basic_bad-source PASS(2, M37M26) DMESG_WARN(1, M26)
ILK igt_kms_setmode_invalid-clone-exclusive-crtc DMESG_WARN(1, M26)PASS(4, M37M26) DMESG_WARN(1, M26)
ILK igt_kms_flip_rcs-wf_vblank-vs-modeset DMESG_WARN(2, M26)PASS(4, M37M26) DMESG_WARN(1, M26)
ILK igt_kms_flip_blocking-absolute-wf_vblank-interruptible DMESG_WARN(2, M26)PASS(3, M37M26) DMESG_WARN(1, M26)
ILK igt_kms_flip_flip-vs-wf_vblank-interruptible DMESG_WARN(1, M26)PASS(2, M37M26) DMESG_WARN(1, M26)
*ILK igt_kms_flip_plain-flip-ts-check-interruptible PASS(2, M37M26) DMESG_WARN(1, M26)
ILK igt_kms_flip_rcs-flip-vs-modeset DMESG_WARN(2, M26)PASS(3, M37M26) DMESG_WARN(1, M26)
ILK igt_kms_flip_vblank-vs-hang TIMEOUT(20, M37M26)PASS(1, M26) TIMEOUT(1, M26)
*ILK igt_kms_flip_wf_vblank-vs-modeset-interruptible PASS(4, M37M26) DMESG_WARN(1, M26)
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-26 13:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-25 22:50 [PATCH] drm: Handle atomic state properly in kms getfoo ioctl Daniel Vetter
2014-11-26 13:00 ` shuang.he [this message]
2014-11-26 15:52 ` Sean Paul
2014-11-26 17:21 ` 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='bf3aaa$indr0u@fmsmga001.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.