The patch titled uml: fix prototypes has been removed from the -mm tree. Its filename was uml-fix-prototypes.patch This patch was dropped because it was merged into mainline or a subsystem tree ------------------------------------------------------ Subject: uml: fix prototypes From: Paolo 'Blaisorblade' Giarrusso <blaisorblade@xxxxxxxx> Declare strlcpy and strlcat more correctly. Signed-off-by: Paolo 'Blaisorblade' Giarrusso <blaisorblade@xxxxxxxx> Cc: Jeff Dike <jdike@xxxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- arch/um/include/user.h | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff -puN arch/um/include/user.h~uml-fix-prototypes arch/um/include/user.h --- a/arch/um/include/user.h~uml-fix-prototypes +++ a/arch/um/include/user.h @@ -14,6 +14,11 @@ */ #define ARRAY_SIZE(x) (sizeof(x) / sizeof((x)[0])) +/* + * This will provide the size_t definition in both kernel and userspace builds + */ +#include <linux/types.h> + extern void panic(const char *fmt, ...) __attribute__ ((format (printf, 1, 2))); extern int printk(const char *fmt, ...) @@ -21,8 +26,7 @@ extern int printk(const char *fmt, ...) extern void schedule(void); extern int in_aton(char *str); extern int open_gdb_chan(void); -/* These use size_t, however unsigned long is correct on both i386 and x86_64. */ -extern unsigned long strlcpy(char *, const char *, unsigned long); -extern unsigned long strlcat(char *, const char *, unsigned long); +extern size_t strlcpy(char *, const char *, size_t); +extern size_t strlcat(char *, const char *, size_t); #endif _ Patches currently in -mm which might be from blaisorblade@xxxxxxxx are origin.patch uml-make-hostfs_setattr-support-operations-on-unlinked-open-files.patch uml-hostfs-style-fixes.patch uml-an-idle-system-should-have-zero-load-average.patch remove-tas.patch x86-create-asm-cmpxchgh.patch uml-network-and-pcap-cleanup.patch uml-pcap-devices-should-get-macs-from-command-line.patch - To unsubscribe from this list: send the line "unsubscribe mm-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html