From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754158AbdKILzd (ORCPT ); Thu, 9 Nov 2017 06:55:33 -0500 Received: from mail-oi0-f67.google.com ([209.85.218.67]:46543 "EHLO mail-oi0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752066AbdKILzb (ORCPT ); Thu, 9 Nov 2017 06:55:31 -0500 X-Google-Smtp-Source: AGs4zMYywi8VW5MCleVABI9awrvEYzI5Pe8XmktF4YVt8VN51Cwh/4/MUood5gOL1aJ19qo0yFoNjp5rMf6Llj55syc= MIME-Version: 1.0 In-Reply-To: References: From: Arnd Bergmann Date: Thu, 9 Nov 2017 12:55:30 +0100 X-Google-Sender-Auth: ZB59oSrHufoyrvGZCubDap1VG70 Message-ID: Subject: Re: [PATCH 3.16 000/294] 3.16.50-rc1 review To: Ben Hutchings Cc: Linux Kernel Mailing List , "# 3.4.x" , Linus Torvalds , Guenter Roeck , Andrew Morton , "kernelci.org bot" Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Nov 7, 2017 at 12:02 AM, Ben Hutchings wrote: > This is the start of the stable review cycle for the 3.16.50 release. > There are 294 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 Fri Nov 08 18:00:00 UTC 2017. > Anything received after that time might be too late. > > A combined patch relative to 3.16.49 will be posted as an additional > response to this. A shortlog and diffstat can be found below. I haven'tr tried building the proposed patches so far, as I was waiting for the kernelci builds. However, I see that the stable-rc/linux-3.16.y doesn't have the current set, it still points to the old 3.16.35 release from last year. I think if you upload the branch to the stable-rc git, that should produce the automated build and boot results via email or via the https://kernelci.org/job/ interface. Once there are some results there, I'll go through the list once more to see what warnings and failures remain. I'm not in a hurry to fix the old warnings, and can do that pass after the 3.16 release is out on git and in kernelci, but it would help to see if the bots has caught any regressions. Arnd