Re: [PATCH 0/22] Introducing asm/syscalls.h
From: Jaswinder Singh
Date: Mon Jul 21 2008 - 02:08:35 EST
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.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/