From: James Hogan <jhogan@kernel.org>
To: Paul Burton <paul.burton@mips.com>
Cc: linux-mips@linux-mips.org, Ralf Baechle <ralf@linux-mips.org>
Subject: Re: [PATCH] MIPS: Wire up io_pgetevents syscall
Date: Fri, 15 Jun 2018 09:35:45 +0100 [thread overview]
Message-ID: <20180615083543.GA7603@jamesdev> (raw)
In-Reply-To: <20180615002946.29757-1-paul.burton@mips.com>
[-- Attachment #1: Type: text/plain, Size: 981 bytes --]
On Thu, Jun 14, 2018 at 05:29:45PM -0700, Paul Burton wrote:
> diff --git a/arch/mips/kernel/scall64-n32.S b/arch/mips/kernel/scall64-n32.S
> index cbf190ef9e8a..8ce8f226e14a 100644
> --- a/arch/mips/kernel/scall64-n32.S
> +++ b/arch/mips/kernel/scall64-n32.S
> @@ -434,4 +434,5 @@ EXPORT(sysn32_call_table)
> PTR sys_pkey_alloc
> PTR sys_pkey_free
> PTR sys_statx /* 6330 */
> + PTR sys_io_pgetevents
> .size sysn32_call_table,.-sysn32_call_table
> diff --git a/arch/mips/kernel/scall64-o32.S b/arch/mips/kernel/scall64-o32.S
> index 9ebe3e2403b1..7b5ce048b1e0 100644
> --- a/arch/mips/kernel/scall64-o32.S
> +++ b/arch/mips/kernel/scall64-o32.S
> @@ -583,4 +583,5 @@ EXPORT(sys32_call_table)
> PTR sys_pkey_alloc
> PTR sys_pkey_free /* 4365 */
> PTR sys_statx
> + PTR sys_io_pgetevents
I wonder if n32 and o32 on 64-bit kernels should use the compat versions
of the io_pgetevents syscall? compat_sys_io_getevents is already used in
these places.
Cheers
James
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2018-06-15 8:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-15 0:29 [PATCH] MIPS: Wire up io_pgetevents syscall Paul Burton
2018-06-15 0:29 ` Paul Burton
2018-06-15 8:35 ` James Hogan [this message]
2018-06-20 3:46 ` [PATCH v2] " Paul Burton
2018-06-20 3:46 ` Paul Burton
2018-06-20 21:17 ` James Hogan
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=20180615083543.GA7603@jamesdev \
--to=jhogan@kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=paul.burton@mips.com \
--cc=ralf@linux-mips.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox