Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755452AbdL2JS2 (ORCPT ); Fri, 29 Dec 2017 04:18:28 -0500 Received: from mail.linuxfoundation.org ([140.211.169.12]:48772 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754830AbdL2JSZ (ORCPT ); Fri, 29 Dec 2017 04:18:25 -0500 Date: Fri, 29 Dec 2017 10:18:28 +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.14 00/74] 4.14.10-stable review Message-ID: <20171229091828.GD18441@kroah.com> References: <20171227164614.109898944@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 Content-Length: 1117 Lines: 31 On Thu, Dec 28, 2017 at 11:29:04AM +0530, Naresh Kamboju wrote: > On 27 December 2017 at 22:15, Greg Kroah-Hartman > wrote: > > This is the start of the stable review cycle for the 4.14.10 release. > > There are 74 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 Fri Dec 29 16:45:52 UTC 2017. > > 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.14.10-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.14.y > > and the diffstat can be found below. > > > > thanks, > > > > greg k-h > > Results from Linaro’s test farm. > No regressions on arm64 and arm. > x86_64 build results will be shared soon in this email thread. I'm guessing x86 is busted for you? Is that a stable patch issue, or an infrastructure issue? thanks, greg k-h