From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from bh-25.webhostbox.net ([208.91.199.152]:52265 "EHLO bh-25.webhostbox.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751666AbbKOOHq (ORCPT ); Sun, 15 Nov 2015 09:07:46 -0500 Subject: Re: [PATCH 3.2 000/164] 3.2.70-rc1 review To: Ben Hutchings , linux-kernel@vger.kernel.org, stable@vger.kernel.org References: <55BD7F2C.4010506@roeck-us.net> <1438552194.3225.54.camel@decadent.org.uk> <55BEECFA.4000105@roeck-us.net> <1447549923.17039.26.camel@decadent.org.uk> Cc: torvalds@linux-foundation.org, Phil Jensen , akpm@linux-foundation.org From: Guenter Roeck Message-ID: <564891AF.5040207@roeck-us.net> Date: Sun, 15 Nov 2015 06:07:43 -0800 MIME-Version: 1.0 In-Reply-To: <1447549923.17039.26.camel@decadent.org.uk> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Sender: stable-owner@vger.kernel.org List-ID: On 11/14/2015 05:12 PM, Ben Hutchings wrote: > On Sun, 2015-08-02 at 21:24 -0700, Guenter Roeck wrote: >> On 08/02/2015 02:49 PM, Ben Hutchings wrote: >>> On Sat, 2015-08-01 at 19:23 -0700, Guenter Roeck wrote: >>>> On 08/01/2015 05:02 PM, Ben Hutchings wrote: >>>>> This is the start of the stable review cycle for the 3.2.70 release. >>>>> There are 164 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 Wed Aug 05 23:00:00 UTC 2015. >>>>> Anything received after that time might be too late. >>>>> >>>> >>>> Build results: >>>> > > > > total: 96 pass: 96 fail: 0 >>>> Qemu test results: >>>> > > > > total: 22 pass: 22 fail: 0 >>>> >>>> Details are available at http://server.roeck-us.net:8010/builders. >>> >>> Thanks. I was checking there as I went along, which is why I added >>> patches 158-160. (It looks like you turned on some new config options >>> for those architectures recently, as the bugs those fix don't seem to >>> be triggered by earlier patches.) >>> >> >> Hi Ben, >> >> I added several 'allnoconfig' and 'allmodconfig' builds. At the same time, >> I changed the approach on how known failures are handled; those are now added >> to an exception list which won't be built in the first place. >> >> The current exception list for builds in 3.2 is: >> >> > alpha:allnoconfig >> > arm:allnoconfig >> > arm:allmodconfig >> > avr32:allnoconfig >> m68k:allnoconfig >> > microblaze:allnoconfig >> > mips:allmodconfig >> openrisc:allnoconfig >> > parisc:allnoconfig >> > sparc32:allmodconfig >> xtensa:defconfig >> > xtensa:allmodconfig >> > xtensa:allnoconfig > > I would be interested to get the arm and mips allmodconfig builds > working if it's not too hard. > I had a look, but I think it is just too hard. Too many changes between 3.2 and 3.10 (which is the first building kernel for arm). Guenter