lkml.org 
[lkml]   [2009]   [Apr]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    Patch in this message
    /
    Date
    From
    Subject[PATCH 5/5] ring-buffer: fix printk output
    From: Steven Rostedt <srostedt@redhat.com>

    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 | 2 +-
    1 files changed, 1 insertions(+), 1 deletions(-)

    diff --git a/kernel/trace/ring_buffer.c b/kernel/trace/ring_buffer.c
    index 9692f10..f4cc590 100644
    --- a/kernel/trace/ring_buffer.c
    +++ b/kernel/trace/ring_buffer.c
    @@ -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,
    --
    1.6.2.1
    --


    \
     
     \ /
      Last update: 2009-04-29 07:03    [W:0.023 / U:179.896 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site