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

[Guenter Roeck]

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

and for qemu tests:

	powerpc:qemu_virtex440_defconfig
	arm:qemu_arm_vexpress_defconfig:vexpress-a15
        arm:multi_v7_defconfig:vexpress-a9
        arm:multi_v7_defconfig:vexpress-a15

There may be more as I am adding more builds.

I didn't expect you to fix any of those. If you are, let me know,
and I'll drop the build/qemu exceptions.

Thanks,
Guenter

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