Re: [PATCH v2 08/29] m68k: assign syscall number for seccomp

From
Geert Uytterhoeven <geert@linux-m68k.org>
Date
2019-01-21 08:57:13
Also in
linux-alpha, linux-api, linux-arch, linux-arm-kernel, linux-fsdevel, linux-mips, linux-s390, linux-sh, lkml, netdev, sparclinux
Reply to
Arnd Bergmann, 2019-01-18
On Fri, Jan 18, 2019 at 5:20 PM Arnd Bergmann [off-list ref] wrote:
Most architectures have assigned a numbers for the seccomp syscall
even when they do not implement it.

m68k is an exception here, so for consistency lets add the number.
Unless CONFIG_SECCOMP is implemented, the system call just
returns -ENOSYS.

Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Acked-by: Geert Uytterhoeven <geert@linux-m68k.org>

Gr{oetje,eeting}s,

                        Geert


--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds
Thread (63 messages) 63 messages, 9 authors, last reply 2019-01-25
Keyboard shortcuts
hback out one level
jnext message in thread / next series-diff position
kprevious message in thread / previous series-diff position
ldrill in
Escclose help / fold thread tree
?toggle this help