From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
"H. Peter Anvin" <hpa@zytor.com>
Cc: linux-next@vger.kernel.org, David Rientjes <rientjes@google.com>
Subject: linux-next: sched tree build warning
Date: Thu, 7 May 2009 11:21:14 +1000 [thread overview]
Message-ID: <20090507112114.d6612ebe.sfr@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 643 bytes --]
Hi all,
Today's linux-next build (powerpc ppc64_defconfig) produced this warning:
kernel/sched.c: In function 'sched_show_task':
kernel/sched.c:6677: warning: format '%08x' expects type 'unsigned int', but argument 5 has type 'long unsigned int'
Introduced by commit 12b5c43486202dd4ff3cfd59a190984a0dd7f6fd ("sched:
emit thread info flags with stack trace") from the sched tree.
thread_info::flags is "unsigned long" on all architectures except alpha
(where it is "unsigned int"), ia64 and x86 (where it is "__u32").
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2009-05-07 1:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-07 1:21 Stephen Rothwell [this message]
2009-05-07 6:45 ` linux-next: sched tree build warning David Rientjes
2009-05-07 7:39 ` Ingo Molnar
-- strict thread matches above, loose matches on Subject: below --
2009-04-21 0:27 Stephen Rothwell
2009-04-21 3:10 ` Gautham R Shenoy
2009-04-21 3:28 ` Stephen Rothwell
2009-04-21 6:09 ` Ingo Molnar
2009-04-21 6:21 ` Rusty Russell
2008-12-22 4:22 Stephen Rothwell
2008-12-22 6:47 ` Ingo Molnar
2008-12-22 6:49 ` Ken Chen
2008-12-22 7:04 ` Ingo Molnar
2008-12-22 7:19 ` Stephen Rothwell
2008-12-22 8:14 ` Paul Mackerras
2008-12-22 8:18 ` Ingo Molnar
2008-12-22 9:44 ` Paul Mackerras
2008-12-22 10:53 ` Ingo Molnar
2008-12-22 12:03 ` Paul Mackerras
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=20090507112114.d6612ebe.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=hpa@zytor.com \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rientjes@google.com \
--cc=tglx@linutronix.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).