From: Juan Quintela <quintela@mandrakesoft.com>
To: linux mips mailing list <linux-mips@linux-mips.org>,
Ralf Baechle <ralf@linux-mips.org>
Subject: [PATCH]: correct format string in dump_tlb
Date: 18 Dec 2002 02:43:37 +0100 [thread overview]
Message-ID: <m2wum8p0dy.fsf@demo.mitica> (raw)
Hi
if we cast to unsigned it, print it as a long is a no-no :(
Later, Juan.
Index: arch/mips/lib/dump_tlb.c
===================================================================
RCS file: /home/cvs/linux/arch/mips/lib/dump_tlb.c,v
retrieving revision 1.8.2.5
diff -u -r1.8.2.5 dump_tlb.c
--- arch/mips/lib/dump_tlb.c 2 Dec 2002 00:24:48 -0000 1.8.2.5
+++ arch/mips/lib/dump_tlb.c 18 Dec 2002 00:49:18 -0000
@@ -179,7 +180,7 @@
#ifdef CONFIG_64BIT_PHYS_ADDR
printk("page == %08Lx\n", (unsigned long long) pte_val(page));
#else
- printk("page == %08lx\n", (unsigned int) pte_val(page));
+ printk("page == %08x\n", (unsigned int) pte_val(page));
#endif
val = pte_val(page);
--
In theory, practice and theory are the same, but in practice they
are different -- Larry McVoy
next reply other threads:[~2002-12-18 1:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-18 1:43 Juan Quintela [this message]
2002-12-18 22:59 ` [PATCH]: correct format string in dump_tlb Ralf Baechle
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=m2wum8p0dy.fsf@demo.mitica \
--to=quintela@mandrakesoft.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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