>> The conflicts on syscall syscall numbers are an unfortunate pain. > > The way we've solved this before is the tree that cares pulls in > the net-next-2.6 tree to resolve the conflict. Actually it seems more common that new syscalls are only added to x86 (plus one or more other architectures that the author cares about). Then arch maintainers throw in a "wire up new syscalls" patch during the merge window when they see these new bits show up. -Tony Oh - ia64 wiring looks good. Acked-by: Tony Luck <tony.luck@xxxxxxxxx> -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
