[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CABeXuvo25MXCxhfMZNgnMaWRXMktQJ7ZKqm-7M70GaGM_54+0g@mail.gmail.com>
Date: Wed, 22 May 2019 15:52:03 -0700
From: Deepa Dinamani <deepa.kernel@...il.com>
To: Chris Down <chris@...isdown.name>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Arnd Bergmann <arnd@...db.de>, axboe@...nel.dk,
Davidlohr Bueso <dave@...olabs.net>, dbueso@...e.de,
Eric Wong <e@...24.org>, Jason Baron <jbaron@...mai.com>,
linux-aio <linux-aio@...ck.org>,
Linux FS-devel Mailing List <linux-fsdevel@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Oleg Nesterov <oleg@...hat.com>,
Omar Kilani <omar.kilani@...il.com>, stable@...r.kernel.org,
Thomas Gleixner <tglx@...utronix.de>,
Alexander Viro <viro@...iv.linux.org.uk>,
linux-mm <linux-mm@...ck.org>
Subject: Re: [PATCH v2] signal: Adjust error codes according to restore_user_sigmask()
On Wed, May 22, 2019 at 3:18 PM Chris Down <chris@...isdown.name> wrote:
>
> +Cc: linux-mm, since this broke mmots tree and has been applied there
>
> This patch is missing a definition for signal_detected in io_cqring_wait, which
> breaks the build.
This patch does not break the build.
The patch the breaks the build was the v2 of this patch since there
was an accidental deletion.
That's what the v3 fixed. I think v3 got picked up today morning into
the mm tree
-Deepa
Powered by blists - more mailing lists