On Sat, 29 Dec 2007, David Brownell wrote: > > There's no way to remove these, which means there's no way to prevent > > lockdep from issuing a warning. > There may be no *efficient* way to do that. If it tracked every lock > individually these false alarms could go away; but that would increase > the overhead to create and destroy such locks too.
And it would also do something completely different compared to what lockdep is doing now. The point is being able to spot the potential deadlock before it actually happens. If you track individual instances instead of classess, you are out of luck with this. -- Jiri Kosina - To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
