From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754253AbdKIMIc (ORCPT ); Thu, 9 Nov 2017 07:08:32 -0500 Received: from out4-smtp.messagingengine.com ([66.111.4.28]:57789 "EHLO out4-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754229AbdKIMIa (ORCPT ); Thu, 9 Nov 2017 07:08:30 -0500 X-ME-Sender: Date: Thu, 9 Nov 2017 13:08:42 +0100 From: Greg KH To: Arnd Bergmann Cc: Ben Hutchings , Linux Kernel Mailing List , "# 3.4.x" , Linus Torvalds , Guenter Roeck , Andrew Morton , "kernelci.org bot" Subject: Re: [PATCH 3.16 000/294] 3.16.50-rc1 review Message-ID: <20171109120842.GA27875@kroah.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.1 (2017-09-22) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Nov 09, 2017 at 12:55:30PM +0100, Arnd Bergmann wrote: > 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. That's because I don't always update the stable-rc tree for other people's releases. I can start doing that, just never have in the past. > 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 don't know of a way to have others push to that tree/branch at the moment :( I'll go update that branch now... greg k-h