public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Will Deacon <will.deacon@arm.com>
To: David Herrmann <dh.herrmann@gmail.com>
Cc: "linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH 2/2] asm-generic: add memfd_create system call to unistd.h
Date: Mon, 11 Aug 2014 18:15:11 +0100	[thread overview]
Message-ID: <20140811171511.GF8828@arm.com> (raw)
In-Reply-To: <CANq1E4Q0gDaJ5XGnkoCQsG8xLh1Q-EBErtEVPpeeZgGj+Nr8dQ@mail.gmail.com>

On Mon, Aug 11, 2014 at 05:54:08PM +0100, David Herrmann wrote:
> On Mon, Aug 11, 2014 at 3:37 PM, Will Deacon <will.deacon@arm.com> wrote:
> > Commit 9183df25fe7b ("shm: add memfd_create() syscall") added a new
> > system call (memfd_create) but didn't update the asm-generic unistd
> > header.
> >
> > This patch adds the new system call to the asm-generic version of
> > unistd.h so that it can be used by architectures such as arm64.
> >
> > Cc: Arnd Bergmann <arnd@arndb.de>
> > Cc: David Herrmann <dh.herrmann@gmail.com>
> > Signed-off-by: Will Deacon <will.deacon@arm.com>
> 
> Reviewed-by: David Herrmann <dh.herrmann@gmail.com>

Thanks, David.

Arnd: shall I take this via the arm64 tree, or do you already have some
asm-generic patches queued?

Will

> > ---
> >  include/uapi/asm-generic/unistd.h | 4 +++-
> >  1 file changed, 3 insertions(+), 1 deletion(-)
> >
> > diff --git a/include/uapi/asm-generic/unistd.h b/include/uapi/asm-generic/unistd.h
> > index f1afd607f043..11d11bc5c78f 100644
> > --- a/include/uapi/asm-generic/unistd.h
> > +++ b/include/uapi/asm-generic/unistd.h
> > @@ -703,9 +703,11 @@ __SYSCALL(__NR_renameat2, sys_renameat2)
> >  __SYSCALL(__NR_seccomp, sys_seccomp)
> >  #define __NR_getrandom 278
> >  __SYSCALL(__NR_getrandom, sys_getrandom)
> > +#define __NR_memfd_create 279
> > +__SYSCALL(__NR_memfd_create, sys_memfd_create)
> >
> >  #undef __NR_syscalls
> > -#define __NR_syscalls 279
> > +#define __NR_syscalls 280
> >
> >  /*
> >   * All syscalls below here should go away really,
> > --
> > 2.0.1
> >
> 

  reply	other threads:[~2014-08-11 17:15 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-11 13:37 [PATCH 1/2] arm64: compat: wire up memfd_create and getrandom syscalls for aarch32 Will Deacon
2014-08-11 13:37 ` [PATCH 2/2] asm-generic: add memfd_create system call to unistd.h Will Deacon
2014-08-11 16:54   ` David Herrmann
2014-08-11 17:15     ` Will Deacon [this message]
2014-08-11 18:57       ` Arnd Bergmann
2014-08-11 19:37         ` Geert Uytterhoeven
2014-08-12 10:27           ` Will Deacon
2014-08-12 11:10             ` Will Deacon
2014-08-12 12:37               ` Vivek Goyal
2014-08-15 13:55                 ` Will Deacon
2014-08-18 17:15                   ` Vivek Goyal
2014-08-18 17:40                     ` Russell King - ARM Linux
2014-08-18 21:04                       ` Vivek Goyal
2014-08-12 10:28         ` Will Deacon
2014-08-11 16:55 ` [PATCH 1/2] arm64: compat: wire up memfd_create and getrandom syscalls for aarch32 David Herrmann

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=20140811171511.GF8828@arm.com \
    --to=will.deacon@arm.com \
    --cc=arnd@arndb.de \
    --cc=dh.herrmann@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@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