From: Randy Dunlap <randy.dunlap@oracle.com>
To: Steven Rostedt <srostedt@redhat.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: linux-next: Tree for March 11 (tracing)
Date: Thu, 12 Mar 2009 09:32:28 -0700 [thread overview]
Message-ID: <49B9391C.8020101@oracle.com> (raw)
In-Reply-To: <1236875181.11290.1.camel@localhost.localdomain>
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.
OK, thanks for the info.
--
~Randy
next prev parent reply other threads:[~2009-03-12 16:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-11 11:59 linux-next: Tree for March 11 Stephen Rothwell
2009-03-11 17:12 ` linux-next: Tree for March 11 (staging/multimedia) Randy Dunlap
2009-03-11 18:11 ` Greg KH
2009-03-11 18:21 ` Randy Dunlap
2009-03-11 18:24 ` Greg KH
2009-03-11 18:27 ` Hans Verkuil
2009-03-11 17:36 ` linux-next: Tree for March 11 (tracing) Randy Dunlap
2009-03-12 16:17 ` Randy Dunlap
2009-03-12 16:26 ` Steven Rostedt
2009-03-12 16:32 ` Randy Dunlap [this message]
2009-03-18 15:46 ` Randy Dunlap
2009-03-18 16:06 ` Ingo Molnar
2009-03-18 16:13 ` Randy Dunlap
2009-03-18 16:32 ` Ingo Molnar
2009-03-18 16:44 ` Randy Dunlap
2009-03-18 16:49 ` Ingo Molnar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49B9391C.8020101@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sfr@canb.auug.org.au \
--cc=srostedt@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.