From: Rich Felker <dalias@libc.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] sh: systemcall wireup
Date: Tue, 31 Jul 2018 14:27:21 +0000 [thread overview]
Message-ID: <20180731142721.GG1392@brightrain.aerifal.cx> (raw)
In-Reply-To: <20180731103609.127718-1-ysato@users.sourceforge.jp>
On Tue, Jul 31, 2018 at 07:36:09PM +0900, Yoshinori Sato wrote:
> Signed-off-by: Yoshinori Sato <ysato@users.sourceforge.jp>
> ---
> arch/sh/include/uapi/asm/unistd_32.h | 8 ++++++--
> arch/sh/kernel/syscalls_32.S | 5 +++++
> 2 files changed, 11 insertions(+), 2 deletions(-)
>
> diff --git a/arch/sh/include/uapi/asm/unistd_32.h b/arch/sh/include/uapi/asm/unistd_32.h
> index 58f04cf3d1d9..4f0fa3ab99f8 100644
> --- a/arch/sh/include/uapi/asm/unistd_32.h
> +++ b/arch/sh/include/uapi/asm/unistd_32.h
> @@ -395,7 +395,11 @@
> #define __NR_copy_file_range 380
> #define __NR_preadv2 381
> #define __NR_pwritev2 382
> -
> -#define NR_syscalls 383
> +#define __NR_pkey_mprotect 383
> +#define __NR_pkey_alloc 384
> +#define __NR_pkey_free 385
> +#define __NR_statx 386
> +#define __NR_io_pgetevents 387
> +#define NR_syscalls 388
>
> #endif /* __ASM_SH_UNISTD_32_H */
> diff --git a/arch/sh/kernel/syscalls_32.S b/arch/sh/kernel/syscalls_32.S
> index 254bc22ee57d..dd2aa16327af 100644
> --- a/arch/sh/kernel/syscalls_32.S
> +++ b/arch/sh/kernel/syscalls_32.S
> @@ -400,3 +400,8 @@ ENTRY(sys_call_table)
> .long sys_copy_file_range /* 380 */
> .long sys_preadv2
> .long sys_pwritev2
> + .long sys_pkey_mprotect
> + .long sys_pkey_alloc
> + .long sys_pkey_free /* 385 */
> + .long sys_statx
> + .long sys_io_pgetevents
> --
> 2.11.0
Looks good. In the next couple days I'm going to start triage of all
the pending patches and get a pull request ready for the next merge,
and I'll make sure to include this.
Rich
prev parent reply other threads:[~2018-07-31 14:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-31 10:36 [PATCH] sh: systemcall wireup Yoshinori Sato
2018-07-31 14:27 ` Rich Felker [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180731142721.GG1392@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=linux-sh@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.