Re: New syscalls (was: Re: linux-next: manual merge of the pidfd tree with the y2038 tree (now block and tip trees))

2019-03-12 Thread Christian Brauner
On March 12, 2019 9:31:33 AM GMT+01:00, Arnd Bergmann wrote: >On Mon, Mar 11, 2019 at 10:43 PM Christian Brauner > wrote: >> On Mon, Mar 11, 2019 at 10:38:07PM +0100, Arnd Bergmann wrote: >> > On Mon, Mar 11, 2019 at 9:36 AM Geert Uytterhoeven > wrote: >> > > >> > > Shall each architcture maintain

Re: New syscalls (was: Re: linux-next: manual merge of the pidfd tree with the y2038 tree (now block and tip trees))

2019-03-12 Thread Arnd Bergmann
On Mon, Mar 11, 2019 at 10:43 PM Christian Brauner wrote: > On Mon, Mar 11, 2019 at 10:38:07PM +0100, Arnd Bergmann wrote: > > On Mon, Mar 11, 2019 at 9:36 AM Geert Uytterhoeven > > wrote: > > > > > > Shall each architcture maintainer take care of this hxxself, or will > > > this be done in > >

Re: New syscalls (was: Re: linux-next: manual merge of the pidfd tree with the y2038 tree (now block and tip trees))

2019-03-11 Thread Christian Brauner
On Mon, Mar 11, 2019 at 10:38:07PM +0100, Arnd Bergmann wrote: > On Mon, Mar 11, 2019 at 9:36 AM Geert Uytterhoeven > wrote: > > On Wed, Feb 13, 2019 at 3:22 PM Arnd Bergmann wrote: > > > On Wed, Feb 13, 2019 at 6:22 AM Stephen Rothwell > > > wrote: > > > > On Tue, 22 Jan 2019 14:10:27 +1100 S

Re: New syscalls (was: Re: linux-next: manual merge of the pidfd tree with the y2038 tree (now block and tip trees))

2019-03-11 Thread Arnd Bergmann
On Mon, Mar 11, 2019 at 9:36 AM Geert Uytterhoeven wrote: > On Wed, Feb 13, 2019 at 3:22 PM Arnd Bergmann wrote: > > On Wed, Feb 13, 2019 at 6:22 AM Stephen Rothwell > > wrote: > > > On Tue, 22 Jan 2019 14:10:27 +1100 Stephen Rothwell > > > wrote: > > > > Today's linux-next merge of the pidfd

New syscalls (was: Re: linux-next: manual merge of the pidfd tree with the y2038 tree (now block and tip trees))

2019-03-11 Thread Geert Uytterhoeven
Hi Arnd, On Wed, Feb 13, 2019 at 3:22 PM Arnd Bergmann wrote: > On Wed, Feb 13, 2019 at 6:22 AM Stephen Rothwell > wrote: > > On Tue, 22 Jan 2019 14:10:27 +1100 Stephen Rothwell > > wrote: > > > Today's linux-next merge of the pidfd tree got conflicts in: > > > > > > arch/x86/entry/syscalls

Re: linux-next: manual merge of the pidfd tree with the y2038 tree (now block and tip trees)

2019-02-13 Thread Arnd Bergmann
On Wed, Feb 13, 2019 at 6:22 AM Stephen Rothwell wrote: > On Tue, 22 Jan 2019 14:10:27 +1100 Stephen Rothwell > wrote: > > > > Today's linux-next merge of the pidfd tree got conflicts in: > > > > arch/x86/entry/syscalls/syscall_32.tbl > > arch/x86/entry/syscalls/syscall_64.tbl > > include/

Re: linux-next: manual merge of the pidfd tree with the y2038 tree (now block and tip trees)

2019-02-12 Thread Stephen Rothwell
Hi all, On Tue, 22 Jan 2019 14:10:27 +1100 Stephen Rothwell wrote: > > Today's linux-next merge of the pidfd tree got conflicts in: > > arch/x86/entry/syscalls/syscall_32.tbl > arch/x86/entry/syscalls/syscall_64.tbl > include/uapi/asm-generic/unistd.h > > between commits: > > 63a96220

Re: linux-next: manual merge of the pidfd tree with the y2038 tree

2019-01-22 Thread Arnd Bergmann
On Tue, Jan 22, 2019 at 1:24 PM Christian Brauner wrote: > On Tue, Jan 22, 2019 at 12:46:56PM +0100, Christian Brauner wrote: > > On Tue, Jan 22, 2019 at 12:42:44PM +0100, Arnd Bergmann wrote: > > > > > > You need to change __NR_syscalls to 425 as well. This will > > > clearly create a conflict, b

Re: linux-next: manual merge of the pidfd tree with the y2038 tree

2019-01-22 Thread Christian Brauner
On Tue, Jan 22, 2019 at 12:46:56PM +0100, Christian Brauner wrote: > On Tue, Jan 22, 2019 at 12:42:44PM +0100, Arnd Bergmann wrote: > > On Tue, Jan 22, 2019 at 11:57 AM Christian Brauner > > wrote: > > > On Tue, Jan 22, 2019 at 11:48:12AM +0100, Arnd Bergmann wrote: > > > > > > Do you mean the a

Re: linux-next: manual merge of the pidfd tree with the y2038 tree

2019-01-22 Thread Christian Brauner
On Tue, Jan 22, 2019 at 12:42:44PM +0100, Arnd Bergmann wrote: > On Tue, Jan 22, 2019 at 11:57 AM Christian Brauner > wrote: > > On Tue, Jan 22, 2019 at 11:48:12AM +0100, Arnd Bergmann wrote: > > > > Do you mean the asm-generic uapi header? In my current series, I do that: > > > > Yes. My idea w

Re: linux-next: manual merge of the pidfd tree with the y2038 tree

2019-01-22 Thread Arnd Bergmann
On Tue, Jan 22, 2019 at 11:57 AM Christian Brauner wrote: > On Tue, Jan 22, 2019 at 11:48:12AM +0100, Arnd Bergmann wrote: > > Do you mean the asm-generic uapi header? In my current series, I do that: > > Yes. My idea was to only change pidfd_send_signal's entry to 424 and > leave the other ones

Re: linux-next: manual merge of the pidfd tree with the y2038 tree

2019-01-22 Thread Christian Brauner
On Tue, Jan 22, 2019 at 11:48:12AM +0100, Arnd Bergmann wrote: > On Tue, Jan 22, 2019 at 11:30 AM Christian Brauner > wrote: > > > > On Tue, Jan 22, 2019 at 10:31:46AM +0100, Christian Brauner wrote: > > > On Tue, Jan 22, 2019 at 10:26:56AM +0100, Arnd Bergmann wrote: > > > > On Mon, Jan 21, 2019

Re: linux-next: manual merge of the pidfd tree with the y2038 tree

2019-01-22 Thread Arnd Bergmann
On Tue, Jan 22, 2019 at 11:30 AM Christian Brauner wrote: > > On Tue, Jan 22, 2019 at 10:31:46AM +0100, Christian Brauner wrote: > > On Tue, Jan 22, 2019 at 10:26:56AM +0100, Arnd Bergmann wrote: > > > On Mon, Jan 21, 2019 at 11:48 PM Christian Brauner > > > wrote: > > > > > > > > On Mon, Jan 21

Re: linux-next: manual merge of the pidfd tree with the y2038 tree

2019-01-22 Thread Christian Brauner
On Tue, Jan 22, 2019 at 10:31:46AM +0100, Christian Brauner wrote: > On Tue, Jan 22, 2019 at 10:26:56AM +0100, Arnd Bergmann wrote: > > On Mon, Jan 21, 2019 at 11:48 PM Christian Brauner > > wrote: > > > > > > On Mon, Jan 21, 2019 at 03:44:17PM -0700, Jens Axboe wrote: > > > > On 1/21/19 1:23 PM,

Re: linux-next: manual merge of the pidfd tree with the y2038 tree

2019-01-22 Thread Christian Brauner
On Tue, Jan 22, 2019 at 10:26:56AM +0100, Arnd Bergmann wrote: > On Mon, Jan 21, 2019 at 11:48 PM Christian Brauner > wrote: > > > > On Mon, Jan 21, 2019 at 03:44:17PM -0700, Jens Axboe wrote: > > > On 1/21/19 1:23 PM, Christian Brauner wrote: > > > > On Mon, Jan 21, 2019 at 09:15:27PM +0100, Arn

Re: linux-next: manual merge of the pidfd tree with the y2038 tree

2019-01-22 Thread Arnd Bergmann
On Mon, Jan 21, 2019 at 11:48 PM Christian Brauner wrote: > > On Mon, Jan 21, 2019 at 03:44:17PM -0700, Jens Axboe wrote: > > On 1/21/19 1:23 PM, Christian Brauner wrote: > > > On Mon, Jan 21, 2019 at 09:15:27PM +0100, Arnd Bergmann wrote: > > >> On Mon, Jan 21, 2019 at 8:13 PM Christian Brauner

linux-next: manual merge of the pidfd tree with the y2038 tree

2019-01-21 Thread Stephen Rothwell
Hi all, Today's linux-next merge of the pidfd tree got conflicts in: arch/x86/entry/syscalls/syscall_32.tbl arch/x86/entry/syscalls/syscall_64.tbl include/uapi/asm-generic/unistd.h between commits: 63a96220ad45 ("arch: add split IPC system calls where needed") 0bd4bb9c5612 ("y2038: ad

Re: linux-next: manual merge of the pidfd tree with the y2038 tree

2019-01-21 Thread Christian Brauner
On Mon, Jan 21, 2019 at 03:44:17PM -0700, Jens Axboe wrote: > On 1/21/19 1:23 PM, Christian Brauner wrote: > > On Mon, Jan 21, 2019 at 09:15:27PM +0100, Arnd Bergmann wrote: > >> On Mon, Jan 21, 2019 at 8:13 PM Christian Brauner > >> wrote: > >>> On Mon, Jan 21, 2019 at 06:16:22PM +0100, Arnd Ber

Re: linux-next: manual merge of the pidfd tree with the y2038 tree

2019-01-21 Thread Jens Axboe
On 1/21/19 1:23 PM, Christian Brauner wrote: > On Mon, Jan 21, 2019 at 09:15:27PM +0100, Arnd Bergmann wrote: >> On Mon, Jan 21, 2019 at 8:13 PM Christian Brauner >> wrote: >>> On Mon, Jan 21, 2019 at 06:16:22PM +0100, Arnd Bergmann wrote: On Mon, Jan 21, 2019 at 4:40 AM Stephen Rothwell >

Re: linux-next: manual merge of the pidfd tree with the y2038 tree

2019-01-21 Thread Christian Brauner
On Mon, Jan 21, 2019 at 09:15:27PM +0100, Arnd Bergmann wrote: > On Mon, Jan 21, 2019 at 8:13 PM Christian Brauner > wrote: > > On Mon, Jan 21, 2019 at 06:16:22PM +0100, Arnd Bergmann wrote: > > > On Mon, Jan 21, 2019 at 4:40 AM Stephen Rothwell > > > wrote: > > > > I plan on sending the pidfd

Re: linux-next: manual merge of the pidfd tree with the y2038 tree

2019-01-21 Thread Arnd Bergmann
On Mon, Jan 21, 2019 at 8:13 PM Christian Brauner wrote: > On Mon, Jan 21, 2019 at 06:16:22PM +0100, Arnd Bergmann wrote: > > On Mon, Jan 21, 2019 at 4:40 AM Stephen Rothwell > > wrote: > > I plan on sending the pidfd branch with the new pidfd_send_signal() > syscall for the 5.1 window. Should w

Re: linux-next: manual merge of the pidfd tree with the y2038 tree

2019-01-21 Thread Christian Brauner
On Mon, Jan 21, 2019 at 06:16:22PM +0100, Arnd Bergmann wrote: > On Mon, Jan 21, 2019 at 4:40 AM Stephen Rothwell > wrote: > > > > Hi all, > > > > Today's linux-next merge of the pidfd tree got conflicts in: > > > > arch/x86/entry/syscalls/syscall_32.tbl > > include/uapi/asm-generic/unistd.h

Re: linux-next: manual merge of the pidfd tree with the y2038 tree

2019-01-21 Thread Arnd Bergmann
On Mon, Jan 21, 2019 at 4:40 AM Stephen Rothwell wrote: > > Hi all, > > Today's linux-next merge of the pidfd tree got conflicts in: > > arch/x86/entry/syscalls/syscall_32.tbl > include/uapi/asm-generic/unistd.h > > between commit: > > 10a9a4dd92e6 ("arch: add split IPC system calls where ne

linux-next: manual merge of the pidfd tree with the y2038 tree

2019-01-20 Thread Stephen Rothwell
Hi all, Today's linux-next merge of the pidfd tree got conflicts in: arch/x86/entry/syscalls/syscall_32.tbl include/uapi/asm-generic/unistd.h between commit: 10a9a4dd92e6 ("arch: add split IPC system calls where needed") b1788424aa2e ("y2038: add 64-bit time_t syscalls to all 32-bit arc