On 4 November 2015 at 16:51, Fabio Estevam <[email protected]> wrote: > Hi Jagan, > > On Wed, Nov 4, 2015 at 9:17 AM, Jagan Teki <[email protected]> wrote: > >> Updated u32 to size_t as prototype uses the same. Does this break? it look >> OK? > > Here is the error I see on Blackfin: > > Building bf518f-ezbrd board... > /home/fabio/.buildman-toolchains/gcc-4.6.3-nolibc/bfin-uclinux/bin/bfin-uclinux-size: > './u-boot': No such file > drivers/mtd/spi/sf_ops.c:655:5: error: conflicting types for 'stm_lock' > drivers/mtd/spi/sf_ops.c:706:5: error: conflicting types for 'stm_unlock' > make[1]: *** [drivers/mtd/spi/sf_ops.o] Error 1 > make: *** [drivers/mtd/spi] Error 2 > drivers/mtd/spi/sf_ops.c:655:5: error: conflicting types for 'stm_lock' > drivers/mtd/spi/sf_internal.h:180:5: note: previous declaration of > 'stm_lock' was here > drivers/mtd/spi/sf_ops.c:706:5: error: conflicting types for 'stm_unlock' > drivers/mtd/spi/sf_internal.h:183:5: note: previous declaration of > 'stm_unlock' was here > make[1]: *** [drivers/mtd/spi/sf_ops.o] Error 1 > > By using size_t we fix this conflicting type error.
Yes true, stm_lock and stm_unlock should use size_t for len - Will update the same. With these all built fine? thanks! -- Jagan | openedev. _______________________________________________ U-Boot mailing list [email protected] http://lists.denx.de/mailman/listinfo/u-boot
