Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1269706

Re: [PATCH 3.2 000/164] 3.2.70-rc1 review

From Guenter Roeck <linux@roeck-us.net>
Newsgroups linux.kernel
Subject Re: [PATCH 3.2 000/164] 3.2.70-rc1 review
Date 2015-11-15 15:10 +0100
Message-ID <qv6ae-2pZ-13@gated-at.bofh.it> (permalink)
References <pSPap-3Sy-3@gated-at.bofh.it> <pSRcd-6Sn-1@gated-at.bofh.it> <pT9su-8bm-13@gated-at.bofh.it> <pTfxU-hP-5@gated-at.bofh.it> <quU93-39Z-1@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Back to linux.kernel | Previous | NextPrevious in thread | Find similar | Unroll thread


Thread

Re: [PATCH 3.2 000/164] 3.2.70-rc1 review Ben Hutchings <ben@decadent.org.uk> - 2015-11-15 02:20 +0100
  Re: [PATCH 3.2 000/164] 3.2.70-rc1 review Guenter Roeck <linux@roeck-us.net> - 2015-11-15 15:10 +0100

csiph-web