All of lore.kernel.org
 help / color / mirror / Atom feed
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, mika.kuoppala@linux.intel.com
Subject: Re: [PATCH] drm/i915: Do kunmap if renderstate parsing fails
Date: 19 Jul 2015 19:51:41 -0700	[thread overview]
Message-ID: <f90827$lpttri@orsmga001.jf.intel.com> (raw)
In-Reply-To: <1437057400-29293-1-git-send-email-mika.kuoppala@intel.com>

Tested-By: Intel Graphics QA PRTS (Patch Regression Test System Contact: shuang.he@intel.com)
Task id: 6815
-------------------------------------Summary-------------------------------------
Platform          Delta          drm-intel-nightly          Series Applied
ILK                                  302/302              302/302
SNB                                  315/315              315/315
IVB                                  342/342              342/342
BYT                                  285/285              285/285
HSW                                  378/378              378/378
-------------------------------------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

      parent reply	other threads:[~2015-07-20  2:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-16 14:36 [PATCH] drm/i915: Do kunmap if renderstate parsing fails Mika Kuoppala
2015-07-16 15:21 ` Siluvery, Arun
2015-07-20  2:51 ` shuang.he [this message]

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$lpttri@orsmga001.jf.intel.com' \
    --to=shuang.he@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 \
    --cc=mika.kuoppala@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.