From: Thomas Chou <thomas@wytron.com.tw>
To: u-boot@lists.denx.de
Subject: [U-Boot] cmd_sf warning on size_t
Date: Wed, 14 Dec 2011 14:36:46 +0800 [thread overview]
Message-ID: <4EE843FE.1070504@wytron.com.tw> (raw)
Hi Mike,
I got this warning on cmd_sf.c,
cmd_sf.c: In function `spi_flash_update_block':
cmd_sf.c:130: warning: unsigned int format, size_t arg (arg 4)
cmd_sf.c:135: warning: unsigned int format, size_t arg (arg 3)
It was related to our arch/avr32|blackfin|nios2/asm/posix_types.h
typedef unsigned long __kernel_size_t;
While most other 32 bits archs use unsigned int, we three use unsigned long.
It is said in linux-2.6/include/asm-generic/posix_types.h
/*
* Most 32 bit architectures use "unsigned int" size_t,
* and all 64 bit architectures use "unsigned long" size_t.
*/
Shall we fix the cmd_sf.c, or shall I change size_t to unsigned int as
other 32 bits archs do?
Best regards,
Thomas
next reply other threads:[~2011-12-14 6:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-14 6:36 Thomas Chou [this message]
2011-12-14 9:34 ` [U-Boot] cmd_sf warning on size_t Andreas Bießmann
2011-12-14 10:04 ` [U-Boot] [PATCH/RFC] fix several printf() modifiers Andreas Bießmann
2011-12-15 2:22 ` Thomas Chou
2011-12-15 2:39 ` Graeme Russ
2011-12-15 5:36 ` Mike Frysinger
2011-12-15 5:35 ` Mike Frysinger
2011-12-15 8:30 ` Andreas Bießmann
2011-12-15 19:22 ` Mike Frysinger
2011-12-15 8:56 ` [U-Boot] [PATCH v2 0/3] fix several printf() length modifers Andreas Bießmann
2011-12-15 8:56 ` [U-Boot] [PATCH v2 1/3] cmd_sf.c: fix printf() length modifier Andreas Bießmann
2011-12-15 12:20 ` Mike Frysinger
2011-12-17 22:56 ` Wolfgang Denk
2011-12-15 8:56 ` [U-Boot] [PATCH v2 2/3] fat.c: " Andreas Bießmann
2011-12-15 12:21 ` Mike Frysinger
2011-12-17 22:56 ` Wolfgang Denk
2011-12-15 8:56 ` [U-Boot] [PATCH v2 3/3] avr32:mmu.c: " Andreas Bießmann
2011-12-15 12:21 ` Mike Frysinger
2011-12-17 22:57 ` Wolfgang Denk
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=4EE843FE.1070504@wytron.com.tw \
--to=thomas@wytron.com.tw \
--cc=u-boot@lists.denx.de \
/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