Re: [PATCH] m68k: Merge mmu and non-mmu versions of sys_call_table

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tuesday 19 April 2011, Arnd Bergmann wrote:
They are already sys_ni_syscall, by means of kernel/sys_ni.c.
I wouldn't bother changing them. The real question is whether
you should define the __NR_* macros for the syscalls that are
not provided. For a new architecture I think you should not,
but removing them might cause regressions. Then again, it's
probably very useful to match the unistd.h file with the system
call table.

I've just looked at the diff between the m68k and m68knommu
syscall tables, and it seems that you should be able to just
use the m68k variant, with a slight adaptation for mmap2/mmap_pgoff.

You might want to use the same method as asm-generic, in order
to provide a way to better synchronize unistd.h and syscalltable.

	Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-m68k" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Video for Linux]     [Yosemite News]     [Linux S/390]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux