From: Aurelien Jarno <aurelien@aurel32.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [4278] Fix wrong type in printf(), introduced in revision 4265
Date: Mon, 28 Apr 2008 20:26:54 +0000 [thread overview]
Message-ID: <E1JqZw6-00073F-HM@cvs.savannah.gnu.org> (raw)
Revision: 4278
http://svn.sv.gnu.org/viewvc/?view=rev&root=qemu&revision=4278
Author: aurel32
Date: 2008-04-28 20:26:54 +0000 (Mon, 28 Apr 2008)
Log Message:
-----------
Fix wrong type in printf(), introduced in revision 4265
Revision Links:
--------------
http://svn.sv.gnu.org/viewvc/?view=rev&root=qemu&revision=4265
Modified Paths:
--------------
trunk/vl.c
Modified: trunk/vl.c
===================================================================
--- trunk/vl.c 2008-04-28 20:26:45 UTC (rev 4277)
+++ trunk/vl.c 2008-04-28 20:26:54 UTC (rev 4278)
@@ -9000,8 +9000,8 @@
if (machine->ram_require & RAMSIZE_FIXED) {
if (ram_size > 0) {
if (ram_size < phys_ram_size) {
- fprintf(stderr, "Machine `%s' requires %i bytes of memory\n",
- machine->name, phys_ram_size);
+ fprintf(stderr, "Machine `%s' requires %llu bytes of memory\n",
+ machine->name, (unsigned long long) phys_ram_size);
exit(-1);
}
reply other threads:[~2008-04-28 20:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=E1JqZw6-00073F-HM@cvs.savannah.gnu.org \
--to=aurelien@aurel32.net \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).