6 new compile/sparse warnings (daily build)

From: John Cherry
Date: Wed Aug 25 2004 - 10:11:04 EST



Compiler: gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)
Arch: i386


Summary:
New warnings = 6
Fixed warnings = 2

New warnings:
-------------
drivers/usb/gadget/inode.c:693:17: warning: incorrect type in assignment
(different type sizes)
drivers/usb/gadget/inode.c:693:17: expected int [usertype] (
*[addressable] [toplevel] ki_retry )( ... )
drivers/usb/gadget/inode.c:693:17: got long ( static [addressable]
[toplevel] *<noident> )( ... )
drivers/usb/gadget/inode.c:693: warning: assignment from incompatible
pointer type

drivers/usb/gadget/inode.c:693:17: warning: incorrect type in assignment
(different type sizes)
drivers/usb/gadget/inode.c:693:17: expected int [usertype] (
*[addressable] [toplevel] ki_retry )( ... )
drivers/usb/gadget/inode.c:693:17: got long ( static [addressable]
[toplevel] *<noident> )( ... )

fs/aio.c:1322:39: warning: incorrect type in argument 2 (different
address spaces)
fs/aio.c:1322:39: expected char [noderef] *<noident><asn:1>
fs/aio.c:1322:39: got char *[addressable] [toplevel] ki_buf

fs/aio.c:1359:40: warning: incorrect type in argument 2 (different
address spaces)
fs/aio.c:1359:40: expected char const [noderef] *<noident><asn:1>
fs/aio.c:1359:40: got char *[addressable] [toplevel] ki_buf

fs/aio.c:1413:7: warning: incorrect type in argument 1 (different
address spaces)
fs/aio.c:1413:7: expected void [noderef] *<noident><asn:1>
fs/aio.c:1413:7: got char *[addressable] [toplevel] ki_buf

fs/aio.c:1425:7: warning: incorrect type in argument 1 (different
address spaces)
fs/aio.c:1425:7: expected void [noderef] *<noident><asn:1>
fs/aio.c:1425:7: got char *[addressable] [toplevel] ki_buf


Fixed warnings:
---------------
security/selinux/hooks.c:2825: warning: `ret' might be used
uninitialized in this function

security/selinux/hooks.c:2886: warning: `ret' might be used
uninitialized in this function



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/