From: Yoshinori Sato <ysato@users.sourceforge.jp>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] sh: system call wire up
Date: Sun, 12 Jun 2016 09:54:07 +0000 [thread overview]
Message-ID: <8760te4ts0.wl-ysato@users.sourceforge.jp> (raw)
In-Reply-To: <1465664789-3976-1-git-send-email-ysato@users.sourceforge.jp>
On Sun, 12 Jun 2016 18:03:13 +0900,
Geert Uytterhoeven wrote:
>
> Hi Sato-san,
>
> On Sat, Jun 11, 2016 at 7:06 PM, Yoshinori Sato
> <ysato@users.sourceforge.jp> wrote:
> > Signed-off-by: Yoshinori Sato <ysato@users.sourceforge.jp>
> > ---
> > arch/sh/include/uapi/asm/unistd_32.h | 16 +++++++++++++++-
> > arch/sh/include/uapi/asm/unistd_64.h | 16 +++++++++++++++-
> > arch/sh/kernel/syscalls_32.S | 14 ++++++++++++++
> > arch/sh/kernel/syscalls_64.S | 14 ++++++++++++++
> > 4 files changed, 58 insertions(+), 2 deletions(-)
> >
> > diff --git a/arch/sh/include/uapi/asm/unistd_32.h b/arch/sh/include/uapi/asm/unistd_32.h
> > index d13a1d6..c801bde 100644
> > --- a/arch/sh/include/uapi/asm/unistd_32.h
> > +++ b/arch/sh/include/uapi/asm/unistd_32.h
> > @@ -380,7 +380,21 @@
> > #define __NR_process_vm_writev 366
> > #define __NR_kcmp 367
> > #define __NR_finit_module 368
> > +#define __NR_sched_getattr 369
> > +#define __NR_sched_setattr 370
> > +#define __NR_renameat2 371
> > +#define __NR_seccomp 372
>
> Doesn't seccomp need architecture support before it can be enabled?
>
> That's the reason why I haven't wired it up on m68k yet.
It automaticaly generate.
But I think "HAVE_ARCH_SECCOMP_FILTER" is not set on sh.
So not rquired architecture support.
> 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
--
Yoshinori Sato
<ysato@users.sourceforge.jp>
next prev parent reply other threads:[~2016-06-12 9:54 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 [this message]
2016-06-12 10:11 ` John Paul Adrian Glaubitz
2016-06-12 11:03 ` Sergei Shtylyov
2016-06-13 13:18 ` Yoshinori Sato
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=8760te4ts0.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).