Geert Uytterhoeven <geert@xxxxxxxxxxxxxx> writes: > Ah, it's the restart_syscall: > > --- include/asm-m68k/unistd.h 2008-10-18 10:34:15.000000000 +0200 > +++ arch/m68knommu/include/asm/unistd.h 2008-10-12 14:08:01.000000000 +0200 > @@ -5,6 +5,7 @@ > * This file contains the system call numbers. > */ > > +#define __NR_restart_syscall 0 > #define __NR_exit 1 > #define __NR_fork 2 > #define __NR_read 3 > @@ -359,9 +360,6 @@ > #define __ARCH_WANT_SYS_SIGPROCMASK > #define __ARCH_WANT_SYS_RT_SIGACTION > > -/* whitelist for checksyscalls */ > -#define __IGNORE_restart_syscall > - > /* > * "Conditional" syscalls > * > > Sorry, I don't know about syscall restart handling, and why it differs. Anyone > who can enlighten me? The syscall restart handling is not yet implemented on m68k(nommu), so there is no real difference. Andreas. -- Andreas Schwab, SuSE Labs, schwab@xxxxxxx SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different." -- To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
