From: shuang.he@intel.com
To: shuang.he@intel.com, ethan.gao@intel.com,
intel-gfx@lists.freedesktop.org, tvrtko.ursulin@linux.intel.com
Subject: Re: [PATCH] drm/i915/skl: Bypass debug message if scalers are not requested
Date: 28 Apr 2015 01:24:40 -0700 [thread overview]
Message-ID: <f90827$ketgen@orsmga001.jf.intel.com> (raw)
In-Reply-To: <1429891698-32164-1-git-send-email-tvrtko.ursulin@linux.intel.com>
Tested-By: Intel Graphics QA PRTS (Patch Regression Test System Contact: shuang.he@intel.com)
Task id: 6262
-------------------------------------Summary-------------------------------------
Platform Delta drm-intel-nightly Series Applied
PNV 276/276 276/276
ILK 301/301 301/301
SNB 318/318 318/318
IVB 345/345 345/345
BYT -2 285/285 283/285
BDW 321/321 321/321
-------------------------------------Detailed-------------------------------------
Platform Test drm-intel-nightly Series Applied
*BYT igt@gem_ctx_basic PASS(3) DMESG_WARN(1)PASS(1)
(dmesg patch applied)drm:check_crtc_state[i915]]*ERROR*mismatch_in_has_infoframe(expected#,found#)@mismatch in has_infoframe .* found
WARNING:at_drivers/gpu/drm/i915/intel_display.c:#check_crtc_state[i915]()@WARNING:.* at .* check_crtc_state+0x
*BYT igt@kms_setmode@invalid-clone-exclusive-crtc PASS(6) DMESG_WARN(1)PASS(1)
(dmesg patch applied)drm:check_crtc_state[i915]]*ERROR*mismatch_in_has_infoframe(expected#,found#)@mismatch in has_infoframe .* found
WARNING:at_drivers/gpu/drm/i915/intel_display.c:#check_crtc_state[i915]()@WARNING:.* at .* check_crtc_state+0x
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:[~2015-04-28 8:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-24 16:08 [PATCH] drm/i915/skl: Bypass debug message if scalers are not requested Tvrtko Ursulin
2015-04-24 16:30 ` Konduru, Chandra
2015-04-24 16:33 ` Tvrtko Ursulin
2015-04-24 17:52 ` Konduru, Chandra
2015-04-24 18:07 ` Konduru, Chandra
2015-05-04 14:29 ` Daniel Vetter
2015-08-05 13:20 ` Tvrtko Ursulin
2015-08-05 13:58 ` Daniel Vetter
2015-08-05 14:12 ` Tvrtko Ursulin
2015-08-05 14:19 ` Tvrtko Ursulin
2015-08-05 15:02 ` Tvrtko Ursulin
2015-04-28 8:24 ` shuang.he [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-08-05 14:14 Tvrtko Ursulin
2015-08-12 5:49 ` shuang.he
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='f90827$ketgen@orsmga001.jf.intel.com' \
--to=shuang.he@intel.com \
--cc=ethan.gao@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=tvrtko.ursulin@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 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.