From: "Randy.Dunlap" <rddunlap@osdl.org>
To: linux-ia64@vger.kernel.org
Subject: [PATCH] smpboot: fix printk type warning
Date: Sat, 23 Aug 2003 06:07:17 +0000 [thread overview]
Message-ID: <marc-linux-ia64-106161914309697@msgid-missing> (raw)
Possibly fallout from cpumask changes (?)....
patch_name: cpus_printk.patch
patch_version: 2003-08-22.22:22:33
author: Randy.Dunlap <rddunlap@osdl.org>
description: fix printk type warning
product: Linux
product_versions: 260-test4
diffstat: arch/ia64/kernel/smpboot.c | 2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
diff -Naur ./arch/ia64/kernel/smpboot.c~cpus ./arch/ia64/kernel/smpboot.c
--- ./arch/ia64/kernel/smpboot.c~cpus Fri Aug 22 16:53:14 2003
+++ ./arch/ia64/kernel/smpboot.c Fri Aug 22 22:20:52 2003
@@ -560,7 +560,7 @@
if (cpu_online(cpu))
bogosum += cpu_data(cpu)->loops_per_jiffy;
- printk(KERN_INFO "Total of %d processors activated (%lu.%02lu BogoMIPS).\n",
+ printk(KERN_INFO "Total of %lu processors activated (%lu.%02lu BogoMIPS).\n",
num_online_cpus(), bogosum/(500000/HZ), (bogosum/(5000/HZ))%100);
}
--
~Randy
next reply other threads:[~2003-08-23 6:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-23 6:07 Randy.Dunlap [this message]
2003-08-25 19:16 ` [PATCH] smpboot: fix printk type warning David Mosberger
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=marc-linux-ia64-106161914309697@msgid-missing \
--to=rddunlap@osdl.org \
--cc=linux-ia64@vger.kernel.org \
/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