public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@ZenIV.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: [git pull] stray signal.git bits
Date: Fri, 10 May 2013 07:19:07 +0100	[thread overview]
Message-ID: <20130510061907.GK25399@ZenIV.linux.org.uk> (raw)

Several syscall-related commits that were missing from the original
pull request.  Please, pull from
git://git.kernel.org/pub/scm/linux/kernel/git/viro/signal for-linus
Shortlog:
Al Viro (3):
      unify compat fanotify_mark(2), switch to COMPAT_SYSCALL_DEFINE
      unicore32: just use mmap_pgoff()...
      switch compat_sys_sysctl to COMPAT_SYSCALL_DEFINE

Alexander van Heukelum (1):
      x86, vm86: fix VM86 syscalls: use SYSCALL_DEFINEx(...)

Diffstat:
 arch/arm64/include/asm/unistd32.h  |    2 +-
 arch/arm64/kernel/sys32.S          |    7 ------
 arch/mips/kernel/linux32.c         |    7 ------
 arch/mips/kernel/scall64-o32.S     |    2 +-
 arch/parisc/kernel/sys_parisc32.c  |    8 -------
 arch/powerpc/kernel/sys_ppc32.c    |    8 -------
 arch/s390/kernel/compat_wrapper.S  |   13 ------------
 arch/s390/kernel/syscalls.S        |    4 +-
 arch/sparc/kernel/sys32.S          |    9 --------
 arch/sparc/kernel/systbls_64.S     |    2 +-
 arch/unicore32/kernel/sys.c        |   10 +--------
 arch/x86/ia32/sys_ia32.c           |    9 --------
 arch/x86/include/asm/sys_ia32.h    |    3 --
 arch/x86/include/asm/syscalls.h    |    4 +-
 arch/x86/kernel/vm86_32.c          |   38 +++++++++++++----------------------
 arch/x86/syscalls/syscall_32.tbl   |    2 +-
 fs/notify/fanotify/fanotify_user.c |   17 ++++++++++++++++
 include/linux/compat.h             |    2 +
 kernel/sys_ni.c                    |    1 +
 kernel/sysctl_binary.c             |    4 +-
 20 files changed, 45 insertions(+), 107 deletions(-)

                 reply	other threads:[~2013-05-10  6:19 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20130510061907.GK25399@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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