From: shuang.he@intel.com
To: shuang.he@intel.com, ethan.gao@intel.com,
intel-gfx@lists.freedesktop.org, peter.antoine@intel.com
Subject: Re: [PATCH] drm: Possible lock priority escalation.
Date: 31 Mar 2015 08:53:49 -0700 [thread overview]
Message-ID: <2d8c1b$kgel6m@fmsmga001.fm.intel.com> (raw)
In-Reply-To: <1427789375-2213-2-git-send-email-peter.antoine@intel.com>
Tested-By: PRC QA PRTS (Patch Regression Test System Contact: shuang.he@intel.com)
Task id: 6099
-------------------------------------Summary-------------------------------------
Platform Delta drm-intel-nightly Series Applied
PNV 276/276 276/276
ILK 303/303 303/303
SNB 304/304 304/304
IVB 338/338 338/338
BYT 287/287 287/287
HSW 361/361 361/361
BDW 309/309 309/309
-------------------------------------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
next prev parent reply other threads:[~2015-03-31 15:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-31 8:09 [PATCH] drm: Kernel Crash in drm_unlock Peter Antoine
2015-03-31 8:09 ` [PATCH] drm: Possible lock priority escalation Peter Antoine
2015-03-31 15:53 ` shuang.he [this message]
2015-03-31 8:09 ` [PATCH] drm: Fixes unsafe deference in locks Peter Antoine
2015-03-31 18:20 ` shuang.he
2015-03-31 13:24 ` [PATCH] drm: Kernel Crash in drm_unlock shuang.he
2015-03-31 13:25 ` Daniel Vetter
2015-03-31 13:28 ` Damien Lespiau
2015-03-31 13:34 ` Antoine, Peter
2015-03-31 14:00 ` Daniel Vetter
2015-03-31 14:21 ` Antoine, Peter
2015-04-15 14:22 ` Antoine, Peter
2015-04-16 7:30 ` Daniel Vetter
2015-03-31 13:35 ` Damien Lespiau
2015-03-31 13:38 ` Antoine, Peter
2015-03-31 13:44 ` Damien Lespiau
2015-03-31 13:47 ` Antoine, Peter
2015-03-31 13:53 ` He, Shuang
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$kgel6m@fmsmga001.fm.intel.com' \
--to=shuang.he@intel.com \
--cc=ethan.gao@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=peter.antoine@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