From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Frank Rowand <frank.rowand@am.sony.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: [ANNOUNCE] 3.0-rt3
Date: Tue, 26 Jul 2011 11:30:29 +0200 [thread overview]
Message-ID: <20110726093029.GR16561@pengutronix.de> (raw)
In-Reply-To: <4E2E306A.6040007@am.sony.com>
On Mon, Jul 25, 2011 at 08:11:38PM -0700, Frank Rowand wrote:
> On 07/24/11 03:33, Thomas Gleixner wrote:
> > Dear RT Folks,
> >
> > I'm pleased to announce the 3.0-rt3 release.
>
> ARM panda board boots for PREEMPT_NONE.
>
> New compile warning for ARM pandaboard, PREEMPT_NONE:
>
> kernel/softirq.c: In function 'softirq_check_pending_idle':
> kernel/softirq.c:119: warning: format '%02lx' expects type 'long unsigned int', but argument 2 has type 'unsigned int'
This happens on x86, too.
The obvious fix is:
diff --git a/kernel/softirq.c b/kernel/softirq.c
index 99620ec..af749f6 100644
--- a/kernel/softirq.c
+++ b/kernel/softirq.c
@@ -77,7 +77,7 @@ char *softirq_to_name[NR_SOFTIRQS] = {
void softirq_check_pending_idle(void)
{
static int rate_limit;
- u32 warnpending = 0, pending = local_softirq_pending();
+ unsigned warnpending = 0, pending = local_softirq_pending();
if (rate_limit >= 10)
return;
@@ -101,7 +101,7 @@ void softirq_check_pending_idle(void)
}
if (warnpending) {
- printk(KERN_ERR "NOHZ: local_softirq_pending %02lx\n",
+ printk(KERN_ERR "NOHZ: local_softirq_pending %02x\n",
pending);
rate_limit++;
}
@@ -115,7 +115,7 @@ void softirq_check_pending_idle(void)
static int rate_limit;
if (rate_limit < 10) {
- printk(KERN_ERR "NOHZ: local_softirq_pending %02lx\n",
+ printk(KERN_ERR "NOHZ: local_softirq_pending %02x\n",
local_softirq_pending());
rate_limit++;
}
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2011-07-26 9:30 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-24 10:33 [ANNOUNCE] 3.0-rt3 Thomas Gleixner
2011-07-24 14:40 ` Maarten Lankhorst
2011-07-24 16:12 ` Thomas Gleixner
2011-07-24 16:42 ` hermann
2011-07-24 16:44 ` Thomas Gleixner
2011-07-24 16:53 ` hermann
2011-07-24 17:23 ` Georgiewskiy Yuriy
2011-07-25 22:20 ` Darren Hart
2011-07-26 6:00 ` Darren Hart
2011-07-26 11:44 ` Maarten Lankhorst
2011-07-26 17:01 ` Darren Hart
2011-07-26 17:11 ` Maarten Lankhorst
2011-07-27 1:57 ` [ANNOUNCE] 3.0-rt3 (futex_requeue bad spinlock magic) Darren Hart
2011-07-27 8:25 ` Darren Hart
2011-07-26 9:01 ` [ANNOUNCE] 3.0-rt3 Thomas Gleixner
2011-07-25 22:55 ` Fernando Lopez-Lezcano
2011-07-26 9:13 ` Uwe Kleine-König
2011-07-26 23:52 ` Fernando Lopez-Lezcano
2011-07-26 23:57 ` Fernando Lopez-Lezcano
2011-07-26 3:11 ` Frank Rowand
2011-07-26 9:30 ` Uwe Kleine-König [this message]
2011-07-26 3:12 ` Frank Rowand
2011-07-26 9:19 ` Uwe Kleine-König
2011-07-26 9:25 ` Thomas Gleixner
2011-07-26 3:14 ` Frank Rowand
2011-07-26 3:49 ` Darren Hart
2011-07-26 6:20 ` Yong Zhang
2011-07-27 18:05 ` N, Mugunthan V
2011-07-27 18:32 ` Thomas Gleixner
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=20110726093029.GR16561@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=frank.rowand@am.sony.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--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