From: Daniel Vetter <daniel@ffwll.ch>
To: shuang.he@intel.com
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/ddi: set has_infoframe flag on DDI too
Date: Wed, 19 Nov 2014 14:53:58 +0100 [thread overview]
Message-ID: <20141119135358.GR25711@phenom.ffwll.local> (raw)
In-Reply-To: <84c8a8$i5qqms@orsmga001.jf.intel.com>
On Tue, Nov 18, 2014 at 04:00:58PM -0800, shuang.he@intel.com wrote:
> Tested-By: PRC QA PRTS (Patch Regression Test System Contact: shuang.he@intel.com)
> -------------------------------------Summary-------------------------------------
> Platform: baseline_drm_intel_nightly_pass_rate->patch_applied_pass_rate
> BYT: pass/total=290/290->290/290
> PNV: pass/total=362/362->362/362
> ILK: pass/total=381/381->381/381
> IVB: pass/total=522/559->522/559
> SNB: pass/total=444/444->444/444
> HSW: pass/total=595/595->595/595
> BDW: pass/total=436/436->435/436
> -------------------------------------Detailed-------------------------------------
> test_platform: test_suite, test_case, result_with_drm_intel_nightly(count, machine_id...)...->result_with_patch_applied(count, machine_id)...
> BDW: Intel_gpu_tools, igt_gem_reset_stats_close-pending-ctx-render, PASS(4, M28) -> FAIL(1, M28)PASS(3, M28)
This patch /should/ fix a pretty decent amount of WARN backtrace in
modeset tests on hsw/bdw (as long as there's a hdmi screen around).
Instead it causes a completely unrelated test to fail.
Can you please dig into what's going on here?
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
_______________________________________________
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-19 13:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-17 21:08 [PATCH 1/2] drm/i915/ddi: set has_infoframe flag on DDI too Jesse Barnes
2014-11-17 21:08 ` [PATCH 2/2] drm/i915/ddi: add break in DDI mode select switch Jesse Barnes
2014-11-18 3:27 ` [PATCH 2/2] drm/i915/ddi: add break in DDI mode select shuang.he
2014-11-18 8:14 ` [PATCH 2/2] drm/i915/ddi: add break in DDI mode select switch Daniel Vetter
2014-11-18 8:14 ` [PATCH 1/2] drm/i915/ddi: set has_infoframe flag on DDI too Daniel Vetter
2014-11-18 16:16 ` Jesse Barnes
2014-11-18 17:45 ` [PATCH] drm/i915/ddi: set has_infoframe flag on DDI too v2 Jesse Barnes
2014-11-19 0:00 ` [PATCH] drm/i915/ddi: set has_infoframe flag on DDI too shuang.he
2014-11-19 13:53 ` Daniel Vetter [this message]
2014-11-19 13:55 ` [PATCH] drm/i915/ddi: set has_infoframe flag on DDI too v2 Daniel Vetter
2014-11-20 15:49 ` Daniel Vetter
2014-11-20 19:54 ` Jesse Barnes
2014-11-20 21:40 ` 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=20141119135358.GR25711@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=shuang.he@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox