Hi Chris,
[auto build test WARNING on drm/drm-next]
[also build test WARNING on next-20161209]
[cannot apply to v4.9-rc8]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
On Sat, Dec 10, 2016 at 10:36 PM, Chris Wilson
wrote:
> On Sat, Dec 10, 2016 at 09:28:02PM +, Chris Wilson wrote:
>> On Sat, Dec 10, 2016 at 09:23:35PM +, Chris Wilson wrote:
>> > On Sat, Dec 10, 2016 at 10:19:30PM +0100, Daniel Vetter wrote:
>> > > On Fri, Dec 09, 2016 at 04:52:32PM
On Fri, Dec 09, 2016 at 04:52:32PM +, Chris Wilson wrote:
> With prime, we are running into false circular dependencies based on the
> order in which two drivers may lock their own struct_mutex wrt to a
> common lock (like the reservation->lock). Work around this by adding the
> lock_class_key
On Sat, Dec 10, 2016 at 09:28:02PM +, Chris Wilson wrote:
> On Sat, Dec 10, 2016 at 09:23:35PM +, Chris Wilson wrote:
> > On Sat, Dec 10, 2016 at 10:19:30PM +0100, Daniel Vetter wrote:
> > > On Fri, Dec 09, 2016 at 04:52:32PM +, Chris Wilson wrote:
> > > > With prime, we are running
On Sat, Dec 10, 2016 at 09:23:35PM +, Chris Wilson wrote:
> On Sat, Dec 10, 2016 at 10:19:30PM +0100, Daniel Vetter wrote:
> > On Fri, Dec 09, 2016 at 04:52:32PM +, Chris Wilson wrote:
> > > With prime, we are running into false circular dependencies based on the
> > > order in which two
On Sat, Dec 10, 2016 at 10:19:30PM +0100, Daniel Vetter wrote:
> On Fri, Dec 09, 2016 at 04:52:32PM +, Chris Wilson wrote:
> > With prime, we are running into false circular dependencies based on the
> > order in which two drivers may lock their own struct_mutex wrt to a
> > common lock (like
