Re: [PATCH 3.4 0/9] 3.4.91-stable review
From: Greg Kroah-Hartman
Date: Sun May 18 2014 - 08:33:14 EST
On Sun, May 18, 2014 at 07:09:12PM +0900, Satoru Takeuchi wrote:
> At Sat, 17 May 2014 08:44:45 -0700,
> Guenter Roeck wrote:
> >
> > On 05/16/2014 03:55 PM, Greg Kroah-Hartman wrote:
> > > This is the start of the stable review cycle for the 3.4.91 release.
> > > There are 9 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 Sun May 18 22:54:50 UTC 2014.
> > > Anything received after that time might be too late.
> > >
> >
> > Build results:
> > total: 134 pass: 109 skipped: 18 fail: 7
> >
> > Qemu tests all passed.
> >
> > There are two new build failures, powerpc:ppc64e_defconfig and powerpc:chroma_defconfig.
> > Those are not due to source code changes, but due to added builds.
> > Failures are seen if the images are built with binutils 2.24, and are caused by a
> > changed assembler ABI. A patch to fix the problem has been submitted but is not yet
> > upstream.
> >
> > Detailed results are available at http://server.roeck-us.net:8010/builders.
> > powerpc builds with binutils 2.24 are shown as 'powerpc_24' architecture.
> >
> > Guenter
> >
>
> This kernel passed my test.
>
> - Test Cases:
> - Build this kernel.
> - Boot this kernel.
> - Build the latest mainline kernel with this kernel.
>
> - Test Tool:
> https://github.com/satoru-takeuchi/test-linux-stable
>
> - Test Result (kernel .config, ktest config and test log):
> http://satoru-takeuchi.org/test-linux-stable/results/<version>-<test datetime>.tar.xz
>
> - Build Environment:
> - OS: Debian Jessy x86_64
> - CPU: Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz x 4
> - memory: 8GB
>
> - Test Target Environment:
> - Debian Jessy x86_64 (KVM guest on the Build Environment)
> - # of vCPU: 2
> - memory: 2GB
Thanks for testing and letting me know.
greg k-h
--
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/