From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] smpboot: fix printk type warning
Date: Mon, 25 Aug 2003 19:16:36 +0000 [thread overview]
Message-ID: <marc-linux-ia64-106183930013686@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106161914309697@msgid-missing>
Randy> Possibly fallout from cpumask changes (?)....
Probably. The patch looks fine to me and I'll apply it.
However, num_online_cpus() is defined in terms of cpus_weight(), which
may expand into hweight32() or hweight64(). hweight32() is declared
to return "unsigned int". The return type for hweight64() doesn't
appear to be totally consistent. E.g., sparc64 returns "unsigned int"
whereas everything else appears to return "unsigned long".
I suspect that, at the lest, cpumask.h should be fixed to return a
fixed type.
--david
Randy> patch_name: cpus_printk.patch
Randy> patch_version: 2003-08-22.22:22:33
Randy> author: Randy.Dunlap <rddunlap@osdl.org>
Randy> description: fix printk type warning
Randy> product: Linux
Randy> product_versions: 260-test4
Randy> diffstat: Randy> arch/ia64/kernel/smpboot.c | 2 +-
Randy> 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
prev parent reply other threads:[~2003-08-25 19:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-23 6:07 [PATCH] smpboot: fix printk type warning Randy.Dunlap
2003-08-25 19:16 ` David Mosberger [this message]
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-106183930013686@msgid-missing \
--to=davidm@napali.hpl.hp.com \
--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