[PATCH v5 01/21] gpu: host1x: Use different lock classes for each client

Dmitry Osipenko digetx at gmail.com
Fri Mar 26 22:47:12 UTC 2021


26.03.2021 22:10, Mikko Perttunen пишет:
> On 3/26/21 8:31 PM, Dmitry Osipenko wrote:
>> 26.03.2021 17:54, Mikko Perttunen пишет:
>>>
>>> Lockdep doesn't seem to be liking dev_name() for the name, and I think
>>> allocating a string for this purpose seems a bit overkill, so I'll keep
>>> the lock name as is if there are no objections.
>>
>> What does "liking" mean?
>>
> 
> kernel/locking/lockdep.c:894 (on my local tree):
> 
>                        WARN_ON_ONCE(class->name != lock->name &&
>                                      lock->key !=
> &__lockdep_no_validate__);

Alright, I see now that lockdep requires to use the same name.



More information about the dri-devel mailing list