From: shuang.he@intel.com
To: shuang.he@intel.com, ethan.gao@intel.com,
intel-gfx@lists.freedesktop.org, ramalingam.c@intel.com
Subject: Re: [PATCH 2/2] drm/i915/drrs: debugfs for notifying the fb status change
Date: 24 Mar 2015 18:24:38 -0700 [thread overview]
Message-ID: <6299f3$kv36r1@orsmga002.jf.intel.com> (raw)
In-Reply-To: <1427132684-27946-3-git-send-email-ramalingam.c@intel.com>
Tested-By: PRC QA PRTS (Patch Regression Test System Contact: shuang.he@intel.com)
Task id: 6032
-------------------------------------Summary-------------------------------------
Platform Delta drm-intel-nightly Series Applied
PNV 275/275 275/275
ILK 303/303 303/303
SNB -1 304/304 303/304
IVB 339/339 339/339
BYT 287/287 287/287
HSW 361/361 361/361
BDW 310/310 310/310
-------------------------------------Detailed-------------------------------------
Platform Test drm-intel-nightly Series Applied
*SNB igt@pm_rpm@fences PASS(2) DMESG_WARN(1)PASS(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-03-25 1:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-23 17:44 [PATCH 0/3] Hack to test DRRS, independent of front buffer tracking Ramalingam C
2015-03-23 17:44 ` [PATCH 1/2] drm/i915: Removing the drrs from front buffer tracker Ramalingam C
2015-03-23 17:44 ` [PATCH 2/2] drm/i915/drrs: debugfs for notifying the fb status change Ramalingam C
2015-03-25 1:24 ` shuang.he [this message]
2015-03-23 17:44 ` [PATCH] tests/kms_drrs: fb change notification through debugfs Ramalingam C
2015-03-24 9:35 ` [PATCH 0/3] Hack to test DRRS, independent of front buffer tracking Daniel Vetter
2015-03-24 9:47 ` Ramalingam C
2015-03-24 10:53 ` 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='6299f3$kv36r1@orsmga002.jf.intel.com' \
--to=shuang.he@intel.com \
--cc=ethan.gao@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ramalingam.c@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.