On m68k, I get: <stdin>:1523:2: warning: #warning syscall recvmmsg not implemented so I started to wire up sys_recvmmsg. Then I noticed it's already accessible, through sys_socketcall, as m68k defines __ARCH_WANT_SYS_SOCKETCALL. So I guess this is a false positive? Surprisingly, several architectures have both defined __ARCH_WANT_SYS_SOCKETCALL and wired up sys_recvmmsg. Is this intentional? Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds -- To unsubscribe from this list: send the line "unsubscribe linux-arch" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html