Re: [GIT PULL] arch: add pidfd and io_uring syscalls everywhere

From: Dmitry V. Levin
Date: Tue Apr 23 2019 - 20:41:50 EST


Hi,

On Tue, Apr 23, 2019 at 09:28:48PM +0200, Arnd Bergmann wrote:
> The following changes since commit 9e98c678c2d6ae3a17cb2de55d17f69dddaa231b:
>
> Linux 5.1-rc1 (2019-03-17 14:22:26 -0700)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/arnd/asm-generic.git
> syscalls-5.1
>
> for you to fetch changes up to 39036cd2727395c3369b1051005da74059a85317:
>
> arch: add pidfd and io_uring syscalls everywhere (2019-04-15 16:31:17 +0200)
>
> ----------------------------------------------------------------
> arch: add pidfd and io_uring syscalls everywhere
>
> This comes a bit late, but should be in 5.1 anyway: we want the newly
> added system calls to be synchronized across all architectures in
> the release.
>
> I hope that in the future, any newly added system calls can be added
> to all architectures at the same time, and tested there while they
> are in linux-next, avoiding dependencies between the architecture
> maintainer trees and the tree that contains the new system call.

Is "everywhere" really means everywhere?
The reason I'm asking this question is that sh64 seems to be excluded:
arch/sh/kernel/syscalls_64.S hasn't got any syscall entries since commit
v4.8-rc1~15^2~3. Is sh64 supported in any way at all?


--
ldv

Attachment: signature.asc
Description: PGP signature