[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <0E75950C-D39C-43F9-950B-284BEA768A90@brauner.io>
Date: Tue, 12 Mar 2019 09:48:11 +0100
From: Christian Brauner <christian@...uner.io>
To: Arnd Bergmann <arnd@...db.de>
CC: Geert Uytterhoeven <geert@...ux-m68k.org>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Jens Axboe <axboe@...nel.dk>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...e.hu>, "H. Peter Anvin" <hpa@...or.com>,
Peter Zijlstra <peterz@...radead.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux-Arch <linux-arch@...r.kernel.org>
Subject: Re: New syscalls (was: Re: linux-next: manual merge of the pidfd tree with the y2038 tree (now block and tip trees))
On March 12, 2019 9:31:33 AM GMT+01:00, Arnd Bergmann <arnd@...db.de> wrote:
>On Mon, Mar 11, 2019 at 10:43 PM Christian Brauner
><christian@...uner.io> 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
><geert@...ux-m68k.org> wrote:
>> > >
>> > > Shall each architcture maintainer take care of this hxxself, or
>will
>> > > this be done in
>> > > a coordinated way?
>> >
>> > I was planning to send a patch for all architectures this time
>> > (after all three sets are merged, which is now), and ask future
>>
>> Just to clarify, are you referring to your sets? I think Linus hasn't
>> gotten around to reviewing the PR for pidfd_send_signal() yet. :)
>
>Ah, I thought he had already merged both, the confusion was on
>my end.
I think I'll do a GIT PULL RESEND later today since I sent the original pr last Tuesday.
Christian
>
> Arnd
Powered by blists - more mailing lists