Re: microblaze syscall list

[Arnd Bergmann]

On Saturday 03 May 2008, Ulrich Drepper wrote:
> Yes, this is how it should be. ÂIt's not done because no architecture
> glibc officially supports arrived after these and similar syscalls
> arrived. ÂThere is no need to implement the not-*at interface, no need
> to implement the creat syscall, etc etc.

Ah, good! So where should the glibc implementation for these calls go?
In the microblaze (and any future architecture) specific source directories,
to be consolidated when you get more of them, or in the common places like
sysdeps/unix/sysv/linux/*.c, with the appropriate #ifndef?

	Arnd <><
--
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/