On Mon, Apr 28, 2014 at 01:43:31PM -0400, Steven Rostedt wrote: > > Peter, > > Things have changed with regard to printk() in linux-next. Now it > appears that lockdep is going haywire over it. I don't understand the > exact reason for the lockdep_off() and lockdep_on() logic that is in > printk(), but it obviously seems to be causing issues with the new > changes. > > Care to take a look?
https://lkml.org/lkml/2011/6/21/247 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/