[U-Boot] __kernel_size_t vs size_t which to use

hey folks,

busy list! Quick question.

I'm trying to build on ! linux and I'm just wondering about the consistency of use of __kernel_size_t vs size_t use in the code base what is 'correct'?

I end up with the a little bit of fallout when I build.

CC arch/arm/cpu/armv7/am33xx/board.o In file included from ../include/linux/compat.h:4:0, from ../include/dm/device.h:17, from ../include/dm.h:10, from ../arch/arm/cpu/armv7/am33xx/board.c:12: ../include/malloc.h:364:7: error: conflicting types for 'memset' void* memset(void*, int, size_t); ^ In file included from ../include/common.h:22:0, from ../arch/arm/cpu/armv7/am33xx/board.c:11: ../include/linux/string.h:78:15: note: previous declaration of 'memset' was here extern void * memset(void *,int,__kernel_size_t);

Quick examination shows we probably want to change the prototype in include/malloc.h to be __kernel_size_t since the various machines posix_types.h appear to be defining the correct width type to that definition (most of the time anyway).

Is this the right thing to do?

Thanks!