ring-buffer: fix printk output
authorSteven Rostedt <srostedt@redhat.com>
Mon, 27 Apr 2009 16:37:49 +0000 (12:37 -0400)
committerSteven Rostedt <rostedt@goodmis.org>
Wed, 29 Apr 2009 04:42:01 +0000 (00:42 -0400)
The warning output in trace_recursive_lock uses %d for a long when
it should be %ld.

[ Impact: fix compile warning ]

Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
kernel/trace/ring_buffer.c

index 9692f100ec1a974cbccf81bf718255f13d1335bf..f4cc59040ebf81337aadab525bae20213529a0a6 100644 (file)
@@ -1491,7 +1491,7 @@ static int trace_recursive_lock(void)
        /* Disable all tracing before we do anything else */
        tracing_off_permanent();
 
-       printk_once(KERN_WARNING "Tracing recursion: depth[%d]:"
+       printk_once(KERN_WARNING "Tracing recursion: depth[%ld]:"
                    "HC[%lu]:SC[%lu]:NMI[%lu]\n",
                    current->trace_recursion,
                    hardirq_count() >> HARDIRQ_SHIFT,