From: shuang.he@intel.com
To: shuang.he@intel.com, lei.a.liu@intel.com,
intel-gfx@lists.freedesktop.org, damien.lespiau@intel.com
Subject: Re: [PATCH 4/4] drm/i915: Don't expose ARGB1555 on gen2/3
Date: 18 May 2015 07:57:07 -0700 [thread overview]
Message-ID: <6299f3$lp9o6e@orsmga002.jf.intel.com> (raw)
In-Reply-To: <1431713163-23900-5-git-send-email-damien.lespiau@intel.com>
Tested-By: Intel Graphics QA PRTS (Patch Regression Test System Contact: shuang.he@intel.com)
Task id: 6420
-------------------------------------Summary-------------------------------------
Platform Delta drm-intel-nightly Series Applied
PNV -1 272/272 271/272
ILK -1 302/302 301/302
SNB -3 315/315 312/315
IVB -11 343/343 332/343
BYT 287/287 287/287
BDW 317/317 317/317
-------------------------------------Detailed-------------------------------------
Platform Test drm-intel-nightly Series Applied
*PNV igt@gem_fence_thrash@bo-write-verify-threaded-none PASS(2) FAIL(1)
*ILK igt@kms_render@direct-render PASS(2) FAIL(1)
*SNB igt@kms_cursor_crc@cursor-size-change PASS(2) FAIL(1)
*SNB igt@pm_rpm@cursor PASS(2) FAIL(1)
SNB igt@pm_rpm@dpms-mode-unset-non-lpsp DMESG_WARN(8)PASS(1) DMESG_WARN(1)
(dmesg patch applied)WARNING:at_drivers/gpu/drm/i915/intel_uncore.c:#assert_device_not_suspended[i915]()@WARNING:.* at .* assert_device_not_suspended+0x
*IVB igt@kms_cursor_crc@cursor-128x128-onscreen PASS(2) FAIL(1)
*IVB igt@kms_cursor_crc@cursor-128x128-random PASS(2) FAIL(1)
*IVB igt@kms_cursor_crc@cursor-128x128-sliding PASS(2) FAIL(1)
*IVB igt@kms_cursor_crc@cursor-256x256-offscreen PASS(2) FAIL(1)
*IVB igt@kms_cursor_crc@cursor-256x256-onscreen PASS(2) FAIL(1)
*IVB igt@kms_cursor_crc@cursor-256x256-sliding PASS(2) FAIL(1)
*IVB igt@kms_cursor_crc@cursor-64x64-offscreen PASS(2) FAIL(1)
*IVB igt@kms_cursor_crc@cursor-64x64-onscreen PASS(2) FAIL(1)
*IVB igt@kms_cursor_crc@cursor-64x64-random PASS(2) FAIL(1)
*IVB igt@kms_cursor_crc@cursor-64x64-sliding PASS(2) FAIL(1)
*IVB igt@kms_cursor_crc@cursor-size-change PASS(2) FAIL(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
prev parent reply other threads:[~2015-05-18 14:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-15 18:05 [PATCH 0/4] Don't say we support framebuffers with alpha when we don't Damien Lespiau
2015-05-15 18:06 ` [PATCH 1/4] drm/i915: Remove the COMMON_PRIMARY_FORMATS defines Damien Lespiau
2015-05-15 18:41 ` Ville Syrjälä
2015-05-15 18:06 ` [PATCH 2/4] drm/i915: Remove ARBG/ABGR 2101010 on platform not supporting those formats Damien Lespiau
2015-05-15 18:44 ` Ville Syrjälä
2015-05-15 18:06 ` [PATCH 3/4] drm/i915: Don't expose RGB/BGR 8888 formats on primary planes before SKL Damien Lespiau
2015-05-15 18:56 ` Ville Syrjälä
2015-05-15 19:15 ` [PATCH v2] " Damien Lespiau
2015-05-19 8:00 ` Daniel Vetter
2015-05-19 11:29 ` [PATCH 3/4 v3] drm/i915: Tighten the exposure ARGB/ABGR 8888 formats Damien Lespiau
2015-05-19 17:01 ` Daniel Vetter
2015-05-15 18:06 ` [PATCH 4/4] drm/i915: Don't expose ARGB1555 on gen2/3 Damien Lespiau
2015-05-15 18:57 ` Ville Syrjälä
2015-05-18 8:34 ` Daniel Vetter
2015-05-18 14:57 ` 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='6299f3$lp9o6e@orsmga002.jf.intel.com' \
--to=shuang.he@intel.com \
--cc=damien.lespiau@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lei.a.liu@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 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.