On Wed, Jul 13, 2016 at 11:06:36AM +0800, Ming Lei wrote: > Now there are several locks which are marked as > no_validate, so name of the lock class can be > different with the no_validate lock.
Hurgh, how did that happen? See checkpatch saying: scripts/checkpatch.pl: "lockdep_no_validate class is reserved for device->mutex.\n" . $herecurr); > This patch avoids this warning for this case, and > fix the following warning: I'm not sure we want that.. given we should strive for less no_validate usage, not more.
