From: shuang.he@intel.com
To: shuang.he@intel.com, julianx.dumez@linux.intel.com,
christophe.sureau@intel.com, lei.a.liu@intel.com,
intel-gfx@lists.freedesktop.org, arun.siluvery@linux.intel.com
Subject: Re: [PATCH] drm/i915/gen9: Update null batch to follow VF state restriction
Date: 10 Aug 2015 14:39:37 -0700 [thread overview]
Message-ID: <f90827$m7bsiq@orsmga001.jf.intel.com> (raw)
In-Reply-To: <1438356525-26820-1-git-send-email-arun.siluvery@linux.intel.com>
Tested-By: Intel Graphics QA PRTS (Patch Regression Test System Contact: shuang.he@intel.com)
Task id: 6912
-------------------------------------Summary-------------------------------------
Platform Delta drm-intel-nightly Series Applied
ILK -1 302/302 301/302
SNB 315/315 315/315
IVB 336/336 336/336
BYT -2 283/283 281/283
HSW 378/378 378/378
-------------------------------------Detailed-------------------------------------
Platform Test drm-intel-nightly Series Applied
*ILK igt@kms_flip@flip-vs-dpms-interruptible PASS(1) DMESG_WARN(1)
*BYT igt@gem_partial_pwrite_pread@reads-uncached PASS(1) FAIL(1)
*BYT igt@gem_persistent_relocs@interruptible PASS(1) 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
next prev parent reply other threads:[~2015-08-10 21:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-31 15:27 [PATCH] tools/null_state/gen9: Send atleast one valid component in VF state Arun Siluvery
2015-07-31 15:28 ` [PATCH] drm/i915/gen9: Update null batch to follow VF state restriction Arun Siluvery
2015-08-05 1:37 ` Ben Widawsky
2015-08-05 7:07 ` Mika Kuoppala
2015-08-10 21:39 ` shuang.he [this message]
2015-08-04 14:03 ` [PATCH] tools/null_state/gen9: Send atleast one valid component in VF state Mika Kuoppala
2015-08-05 1:36 ` Ben Widawsky
2015-08-05 8:13 ` Mika Kuoppala
2015-08-05 18:17 ` Ben Widawsky
2015-08-13 12:30 ` Mika Kuoppala
2015-08-13 13:11 ` [PATCH] tools/null_state/gen9: Send all components " Mika Kuoppala
2015-08-17 16:54 ` Ben Widawsky
2015-11-06 22:00 ` Chris Wilson
2015-11-06 22:19 ` Ben Widawsky
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$m7bsiq@orsmga001.jf.intel.com' \
--to=shuang.he@intel.com \
--cc=arun.siluvery@linux.intel.com \
--cc=christophe.sureau@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=julianx.dumez@linux.intel.com \
--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.