public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: shuang.he@intel.com
To: shuang.he@intel.com, ethan.gao@intel.com,
	intel-gfx@lists.freedesktop.org, chris@chris-wilson.co.uk
Subject: Re: [PATCH] drm/i915: Store device pointer in contexts for late tracepoint usafe
Date: 05 May 2015 05:00:09 -0700	[thread overview]
Message-ID: <2d8c1b$l0pban@fmsmga001.fm.intel.com> (raw)
In-Reply-To: <1430813849-25117-1-git-send-email-chris@chris-wilson.co.uk>

Tested-By: Intel Graphics QA PRTS (Patch Regression Test System Contact: shuang.he@intel.com)
Task id: 6317
-------------------------------------Summary-------------------------------------
Platform          Delta          drm-intel-nightly          Series Applied
PNV                                  276/276              276/276
ILK                                  302/302              302/302
SNB                                  316/316              316/316
IVB                                  342/342              342/342
BYT                                  286/286              286/286
BDW                                  318/318              318/318
-------------------------------------Detailed-------------------------------------
Platform  Test                                drm-intel-nightly          Series Applied
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

  reply	other threads:[~2015-05-05 12:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-05  8:17 [PATCH] drm/i915: Store device pointer in contexts for late tracepoint usafe Chris Wilson
2015-05-05 12:00 ` shuang.he [this message]
2015-05-06 11:16 ` Daniel Vetter
2015-05-07  9:57   ` Chris Wilson
2015-06-29 11:40     ` Jani Nikula
2015-06-29 11:41       ` Chris Wilson
2015-06-29 11:49         ` Jani Nikula
2015-07-09  9:41           ` Ceraolo Spurio, Daniele
2015-07-09 15:19             ` 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='2d8c1b$l0pban@fmsmga001.fm.intel.com' \
    --to=shuang.he@intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=ethan.gao@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    /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