Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753911AbeAIKuv (ORCPT + 1 other); Tue, 9 Jan 2018 05:50:51 -0500 Received: from mail.linuxfoundation.org ([140.211.169.12]:43836 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750913AbeAIKut (ORCPT ); Tue, 9 Jan 2018 05:50:49 -0500 Date: Tue, 9 Jan 2018 11:50:51 +0100 From: Greg Kroah-Hartman To: Naresh Kamboju Cc: linux-kernel@vger.kernel.org, Linus Torvalds , Andrew Morton , Guenter Roeck , Shuah Khan , patches@kernelci.org, Ben Hutchings , lkft-triage@lists.linaro.org, linux- stable , Tom Gall Subject: Re: [PATCH 4.4 00/22] 4.4.111-stable review Message-ID: <20180109105051.GA28127@kroah.com> References: <20180108125925.601688333@linuxfoundation.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.9.2 (2017-12-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: On Tue, Jan 09, 2018 at 03:21:35PM +0530, Naresh Kamboju wrote: > On 8 January 2018 at 18:29, Greg Kroah-Hartman > wrote: > > This is the start of the stable review cycle for the 4.4.111 release. > > There are 22 patches in this series, all will be posted as a response > > to this one. If anyone has any issues with these being applied, please > > let me know. > > > > Responses should be made by Wed Jan 10 12:59:14 UTC 2018. > > Anything received after that time might be too late. > > > > The whole patch series can be found in one patch at: > > kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.4.111-rc1.gz > > or in the git tree and branch at: > > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-4.4.y > > and the diffstat can be found below. > > > > thanks, > > > > greg k-h > > Results from Linaro’s test farm. > No regressions on arm64, arm and x86_64. > > NOTE: > There were multiple pushes to 4.4.111-rc1 here is what we have the > latest results. > We will report results again soon with latest builds. I just pushed a build-fix that you aren't seeing, but it should work the same as what you have already tested (i.e. it only fixed a build problem.) thanks, greg k-h