From: Ingo Molnar <mingo@elte•hu>
To: David Rientjes <rientjes@google•com>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
Thomas Gleixner <tglx@linutronix•de>,
"H. Peter Anvin" <hpa@zytor•com>,
linux-next@vger•kernel.org
Subject: Re: linux-next: sched tree build warning
Date: Thu, 7 May 2009 09:39:20 +0200 [thread overview]
Message-ID: <20090507073920.GB18125@elte.hu> (raw)
In-Reply-To: <alpine.DEB.2.00.0905062341420.22671@chino.kir.corp.google.com>
* David Rientjes <rientjes@google•com> wrote:
> On Thu, 7 May 2009, Stephen Rothwell wrote:
>
> > 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").
> >
>
> Thanks Stephen. There's a hacky way around this if Ingo will put
> up with it.
> - printk(KERN_CONT "%5lu %5d %6d 0x%08x\n", free,
> + printk(KERN_CONT "%5lu %5d %6d 0x%08lx\n", free,
> task_pid_nr(p), task_pid_nr(p->real_parent),
> - task_thread_info(p)->flags);
> + (unsigned long)task_thread_info(p)->flags);
applied, thanks.
Ingo
next prev parent reply other threads:[~2009-05-07 7:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-07 1:21 linux-next: sched tree build warning Stephen Rothwell
2009-05-07 6:45 ` David Rientjes
2009-05-07 7:39 ` Ingo Molnar [this message]
-- 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=20090507073920.GB18125@elte.hu \
--to=mingo@elte$(echo .)hu \
--cc=hpa@zytor$(echo .)com \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=rientjes@google$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=tglx@linutronix$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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