Re: linux-next: Tree for March 11 (tracing)

[Randy Dunlap]

Ingo Molnar wrote:
> * Randy Dunlap <randy.dunlap@xxxxxxxxxx> wrote:
> 
>> On Thu, 12 Mar 2009 12:26:21 -0400 Steven Rostedt wrote:
>>
>>> On Thu, 2009-03-12 at 09:17 -0700, Randy Dunlap wrote:
>>>> [adding cc:s]
>>>>
>>>> [same report for March 12]
>>>>
>>>> Randy Dunlap wrote:
>>>>> Stephen Rothwell wrote:
>>>>>> Hi all,
>>>>>>
>>>>>> Changes since 20090310:
>>>>>
>>>>> Building on i386 generates a ton of printk format warnings:
>>>>>
>>>>> kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 5 has type 'unsigned int'
>>>>> kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 6 has type 'unsigned int'
>>>>> kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 9 has type 'unsigned int'
>>>>> kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 10 has type 'unsigned int'
>>>>> kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 13 has type 'unsigned int'
>>>>> kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 14 has type 'unsigned int'
>>>>> kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 17 has type 'unsigned int'
>>>>> kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 18 has type 'unsigned int'
>>>>> kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 21 has type 'unsigned int'
>>>>> kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 22 has type 'unsigned int'
>>>>>
>>> I believe this is corrected in Ingo's tip tree. I changed %lu to %zu to
>>> handle the "sizeof()" case. The fix was suggested by Andrew Morton.
>>
>> This build warning is still around (20090318).
>> Is the fix not in some branch that is imported into linux-next or what?
> 
> be patient.
> 
> 	Ingo

I think that 7 days is being patient for a simple build fix.

Thanks.
-- 
~Randy
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/