[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAG48ez0nyLsyAeLJXEnCnhkh26EnZGnam1cyd84a5LoFcEyMiw@mail.gmail.com>
Date: Fri, 24 Apr 2020 01:59:47 +0200
From: Jann Horn <jannh@...gle.com>
To: Ben Hutchings <ben@...adent.org.uk>
Cc: kernel list <linux-kernel@...r.kernel.org>,
stable <stable@...r.kernel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Guenter Roeck <linux@...ck-us.net>,
Andrew Morton <akpm@...ux-foundation.org>,
Denis Kirjanov <kda@...ux-powerpc.org>
Subject: Re: [PATCH 3.16 000/245] 3.16.83-rc1 review
On Fri, Apr 24, 2020 at 1:03 AM Ben Hutchings <ben@...adent.org.uk> wrote:
> This is the start of the stable review cycle for the 3.16.83 release.
> There are 245 patches in this series, which will be posted as responses
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses should be made by Tue Apr 28 18:00:00 UTC 2020.
> Anything received after that time might be too late.
Can you please add backports of the following patches? I asked for
that in <https://lore.kernel.org/stable/CAG48ez29d-JJOw8XMp1Z=7sDj8Kvmt+9KXC9-ux-0OBhUP02Xg@mail.gmail.com/>,
but I guess that fell through the cracks somehow.
8019ad13ef7f64be44d4f892af9c840179009254 "futex: Fix inode life-time issue"
8d67743653dce5a0e7aa500fcccb237cde7ad88e "futex: Unbreak futex hashing"
Can those still go into 3.16.83, or is it too late for that now?
Powered by blists - more mailing lists