Thanks.
Tony, this reminds me a comment that you made some time ago, when I
sent to the linux-ia64 patches to add accept4() syscall that was
equally forgotten in it's time.
Here's what you were saying to me by mail on September 1st, 2012:
"Hmmm. I looked into this a bit further - and found that I hadn't
seen a warning about the missing accept4() system call from
scripts/checksyscalls.sh because it just compares against the x86_32
list - and accept4() isn't there."
Hence my question: Was it also the case for kcmp() syscall? If yes,
what could be done to ensure that such miss at adding syscall can be
avoided in the future?
Émeric
2015-10-28 23:12 GMT+01:00 Luck, Tony <tony.luck@xxxxxxxxx>:
> The following changes since commit 32b88194f71d6ae7768a29f87fbba454728273ee:
>
> Linux 4.3-rc7 (2015-10-25 10:39:47 +0900)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/aegl/linux.git tags/please-pull-syscalls
>
> for you to fetch changes up to d305c4773458fdd6ff9c52bfdea8c67fbd3b2072:
>
> [IA64] Wire up kcmp syscall (2015-10-28 14:22:59 -0700)
>
> ----------------------------------------------------------------
> Missed adding the kcmp() syscall a long time ago. Now it seems
> that it is essential to build systemd.
>
> ----------------------------------------------------------------
> Émeric MASCHINO (1):
> [IA64] Wire up kcmp syscall
>
> arch/ia64/include/asm/unistd.h | 2 +-
> arch/ia64/include/uapi/asm/unistd.h | 1 +
> arch/ia64/kernel/entry.S | 1 +
> 3 files changed, 3 insertions(+), 1 deletion(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
|