On Mon, Jul 21, 2008 at 11:37:14AM +0530, Jaswinder Singh wrote: > ???linux/syscalls.h is Linux syscall interfaces (non-arch-specific) > > So asm/syscalls.h is ???Linux syscall interfaces (arch-specific) That's how you see it. > 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. sys_fork() does seem to be the worst case scenario. I suspect there's similar ones (clone?). I still think it's worth adding them all to linux/syscalls.h. -- Intel are signing my paycheques ... these opinions are still mine "Bill, look, we understand that you're interested in selling us this operating system, but compare it to ours. We can't possibly take such a retrograde step." -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
