printk: Do not disable preemption for accessing printk_func
authorSteven Rostedt (Red Hat) <rostedt@goodmis.org>
Thu, 11 Dec 2014 14:12:01 +0000 (09:12 -0500)
committerSteven Rostedt <rostedt@goodmis.org>
Thu, 11 Dec 2014 14:12:01 +0000 (09:12 -0500)
As printk_func will either be the default function, or a per_cpu function
for the current CPU, there's no reason to disable preemption to access
it from printk. That's because if the printk_func is not the default
then the caller had better disabled preemption as they were the one to
change it.

Link: http://lkml.kernel.org/r/CA+55aFz5-_LKW4JHEBoWinN9_ouNcGRWAF2FUA35u46FRN-Kxw@mail.gmail.com
Suggested-by: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>

No differences found