Hello Matthew, On Sun, 2008-07-20 at 23:55 -0600, Matthew Wilcox wrote: > I think it makes more sense to add them to linux/syscall.h, possibly > with comments mentioning which architectures implement them. > > If there are architectures with different prototypes for the same > syscall, using an ifdef CONFIG_(arch) is /better/ annotation that having > them in different header files. > linux/syscalls.h is Linux syscall interfaces (non-arch-specific) So asm/syscalls.h is Linux syscall interfaces (arch-specific) And if we add all arch dependent syscalls.h in linux/syscalls then it will be very complex and do not look nice, for example sys_fork is keep on changing for many architecture. Thank you, Jaswinder Singh. -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
