All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yoshinori Sato <ysato@users.sourceforge.jp>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] sh: system call wire up
Date: Mon, 13 Jun 2016 13:18:20 +0000	[thread overview]
Message-ID: <87lh29dy77.wl-ysato@users.sourceforge.jp> (raw)
In-Reply-To: <1465664789-3976-1-git-send-email-ysato@users.sourceforge.jp>

On Sun, 12 Jun 2016 20:03:08 +0900,
Sergei Shtylyov wrote:
> 
> Hello.
> 
> On 6/11/2016 8:06 PM, Yoshinori Sato wrote:
> 
> > Signed-off-by: Yoshinori Sato <ysato@users.sourceforge.jp>
> 
> [...]
> >  #endif /* __ASM_SH_UNISTD_64_H */
> > diff --git a/arch/sh/kernel/syscalls_32.S b/arch/sh/kernel/syscalls_32.S
> > index 734234b..f03a16b 100644
> > --- a/arch/sh/kernel/syscalls_32.S
> > +++ b/arch/sh/kernel/syscalls_32.S
> > @@ -386,3 +386,17 @@ ENTRY(sys_call_table)
> >  	.long sys_process_vm_writev
> >  	.long sys_kcmp
> >  	.long sys_finit_module
> > +	.long sys_sched_getattr
> > +	.long sys_sched_getattr		/* 370 */
> 
>    Not sys_sched_setattr?

Ouch.
Yes. I mistake.
I will send v2.

> > +	.long sys_renameat2
> > +	.long sys_seccomp
> > +	.long sys_getrandom
> > +	.long sys_memfd_create
> > +	.long sys_bpf			/* 375 */
> > +	.long sys_execveat
> > +	.long sys_userfaultfd
> > +	.long sys_membarrier
> > +	.long sys_mlock2
> > +	.long sys_copy_file_range	/* 380 */
> > +	.long sys_preadv2
> > +	.long sys_pwritev2
> > diff --git a/arch/sh/kernel/syscalls_64.S b/arch/sh/kernel/syscalls_64.S
> > index 579fcb9..7e79252 100644
> > --- a/arch/sh/kernel/syscalls_64.S
> > +++ b/arch/sh/kernel/syscalls_64.S
> > @@ -406,3 +406,17 @@ sys_call_table:
> >  	.long sys_process_vm_writev
> >  	.long sys_kcmp
> >  	.long sys_finit_module
> > +	.long sys_sched_getattr		/* 380 */
> > +	.long sys_sched_getattr
> 
>    Not sys_sched_setattr?
> 
> > +	.long sys_renameat2
> > +	.long sys_seccomp
> > +	.long sys_getrandom
> > +	.long sys_memfd_create		/* 385 */
> > +	.long sys_bpf
> > +	.long sys_execveat
> > +	.long sys_userfaultfd
> > +	.long sys_membarrier
> > +	.long sys_mlock2		/* 390 */
> > +	.long sys_copy_file_range
> > +	.long sys_preadv2
> > +	.long sys_pwritev2
> 
> MBR, Serei
> 

-- 
Yoshinori Sato
<ysato@users.sourceforge.jp>

      parent reply	other threads:[~2016-06-13 13:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-11 17:06 [PATCH] sh: system call wire up Yoshinori Sato
2016-06-11 21:32 ` John Paul Adrian Glaubitz
2016-06-12  9:03 ` Geert Uytterhoeven
2016-06-12  9:54 ` Yoshinori Sato
2016-06-12 10:11 ` John Paul Adrian Glaubitz
2016-06-12 11:03 ` Sergei Shtylyov
2016-06-13 13:18 ` Yoshinori Sato [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=87lh29dy77.wl-ysato@users.sourceforge.jp \
    --to=ysato@users.sourceforge.jp \
    --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.