From: Ulrich Eckhardt <eckhardt@satorlaser.com>
To: linux-mips@linux-mips.org
Subject: Re: [PATCH] fix some compiler warnings (field width, unused variable)
Date: Wed, 7 Jun 2006 11:03:34 +0200 [thread overview]
Message-ID: <200606071103.34646.eckhardt@satorlaser.com> (raw)
In-Reply-To: <20060602.015404.93020143.anemo@mba.ocn.ne.jp>
On Thursday 01 June 2006 18:54, Atsushi Nemoto wrote:
> printk("initrd extends beyond end of memory "
> - "(0x%0*Lx > 0x%0*Lx)\ndisabling initrd\n",
> - width,
> - (unsigned long long) CPHYSADDR(initrd_end),
> - width,
> - (unsigned long long) PFN_PHYS(max_low_pfn));
> + "(0x%p > 0x%p)\ndisabling initrd\n",
> + (void *)CPHYSADDR(initrd_end),
> + (void *)PFN_PHYS(max_low_pfn));
I'm not so sure if this is a good idea because some systems have 36 bit
physical addresses while they only have 32 bit void pointers, so long long is
probably really the better solution.
I'm wondering if it would be worth having a special flag in printk to indicate
a physical address ("%lp" perhaps?) so that you don't get the unimportant
leading zeroes for the bits 36 to 63 for above mentioned platforms.
Uli
****************************************************
Visit our website at <http://www.domino-printing.com/>
****************************************************
This Email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this Email in error please notify the system manager.
This footnote also confirms that this Email message has been swept by MailSweeper for the presence of computer viruses.
****************************************************
next prev parent reply other threads:[~2006-06-07 9:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-31 16:00 [PATCH] fix some compiler warnings (field width, unused variable) Atsushi Nemoto
2006-05-31 16:47 ` Geert Uytterhoeven
2006-06-01 16:54 ` Atsushi Nemoto
2006-06-07 9:03 ` Ulrich Eckhardt [this message]
2006-06-07 14:58 ` Atsushi Nemoto
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=200606071103.34646.eckhardt@satorlaser.com \
--to=eckhardt@satorlaser.com \
--cc=linux-mips@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.