[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 4 Apr 2019 09:28:03 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: linux-kernel@...r.kernel.org
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Ingo Molnar <mingo@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Andy Lutomirski <luto@...capital.net>,
Roland McGrath <roland@...k.frob.com>,
Oleg Nesterov <oleg@...hat.com>, linux-arch@...r.kernel.org,
Peter Zijlstra <peterz@...radead.org>,
Thomas Gleixner <tglx@...utronix.de>,
"Gustavo A. R. Silva" <gustavo@...eddedor.com>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
"H. Peter Anvin" <hpa@...or.com>, x86@...nel.org,
Dominik Brodowski <linux@...inikbrodowski.net>,
Andy Lutomirski <luto@...nel.org>,
Kees Cook <keescook@...omium.org>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
"Dmitry V. Levin" <ldv@...linux.org>,
Palmer Dabbelt <palmer@...ive.com>
Subject: Re: [PATCH 0/6 v3] sycalls: Remove args i and n from
syscall_get_arguments()
On Mon, 01 Apr 2019 09:41:04 -0400
Steven Rostedt <rostedt@...dmis.org> wrote:
> [ Looking for acks ]
>
I got a couple.
> Two and a half years ago I sent out 3 patches and a title letter that
> had this[1]:
Linus,
Is this something that can go into this -rc release or would you want
me to wait till the next merge window?
The reason I ask, is that there's two arch patches in this series that
have stable tags attached to them. But I moved things around such that
they are applied before the global arch patches are and can be applied
independently.
Should I move those two patches up front and just add those to this
release cycle, or would you like the entire series now?
-- Steve
> ----
> arch/arc/include/asm/syscall.h | 7 +-
> arch/arm/include/asm/syscall.h | 47 ++---------
> arch/arm64/include/asm/syscall.h | 46 ++---------
> arch/c6x/include/asm/syscall.h | 79 ++++---------------
> arch/csky/include/asm/syscall.h | 26 ++-----
> arch/h8300/include/asm/syscall.h | 34 ++------
> arch/hexagon/include/asm/syscall.h | 4 +-
> arch/ia64/include/asm/syscall.h | 13 +---
> arch/ia64/kernel/ptrace.c | 7 +-
> arch/microblaze/include/asm/syscall.h | 8 +-
> arch/mips/include/asm/syscall.h | 3 +-
> arch/mips/kernel/ptrace.c | 2 +-
> arch/nds32/include/asm/syscall.h | 62 +++------------
> arch/nios2/include/asm/syscall.h | 84 ++++----------------
> arch/openrisc/include/asm/syscall.h | 12 +--
> arch/parisc/include/asm/syscall.h | 30 ++-----
> arch/powerpc/include/asm/syscall.h | 15 ++--
> arch/riscv/include/asm/syscall.h | 24 ++----
> arch/s390/include/asm/syscall.h | 28 +++----
> arch/sh/include/asm/syscall_32.h | 47 +++--------
> arch/sh/include/asm/syscall_64.h | 8 +-
> arch/sparc/include/asm/syscall.h | 11 ++-
> arch/um/include/asm/syscall-generic.h | 78 +++----------------
> arch/x86/include/asm/syscall.h | 142 ++++++++--------------------------
> arch/xtensa/include/asm/syscall.h | 33 ++------
> fs/proc/base.c | 17 ++--
> include/asm-generic/syscall.h | 21 ++---
> include/linux/ptrace.h | 11 ++-
> include/trace/events/syscalls.h | 2 +-
> kernel/seccomp.c | 2 +-
> kernel/trace/trace_syscalls.c | 9 ++-
> lib/syscall.c | 57 ++++++--------
> 32 files changed, 247 insertions(+), 722 deletions(-)
Powered by blists - more mailing lists