Re: [PATCH 0/9] kernel-yocto: consolidated pull request

Bruce Ashfield
2017-08-21T15:57:20Z

On 2017-08-21 11:55 AM, Richard Purdie wrote:
> On Sun, 2017-08-20 at 22:58 -0400, Bruce Ashfield wrote:
>> Here's the collected set of kernel changes that are ready for the M3
>> builds.
>>
>> We have some kernel meta data changes:
>>
>>   kernel-yocto: configuration updates: x86 features
>>   linux-yocto/4.1: fix fsl-ls10xx sdhci
>>   linux-yocto: add usb-net configs by default
>>
>> Some bug fixes:
>>
>>   kernel-yocto: ensure that only valid BSPs are built
>>   linux-yocto/4.10: CVE & misc fixes
>>
>> And the important changes are the addition of the 4.12 kernel + libc headers
>> and the removal of the 4.1 kernel.
>>
>> I also have some -stable updates queued for the active kernel versions, but
>> they will come out once this series has made it into the tree, since I'm
>> trying to isolate any 4.12 issues from other -stable updates.
>>
>> I built and booted all the qemu targets for 4.12, and have built for
>> core-image-sato, core-image-kernel-dev, glibc and muslc for all of the
>> architectures. My testing didn't pick up any regressions, but I was battling
>> some other build errors (non kernel related) during my testing, so I can
>> never be 100% sure.
>>
>> I've sent patches to poky to remove/bump any references to the 4.1 kernel
>> .. if I've missed any, I'm sure people will shout.
>
> Thanks for the other fix, not got that tested yet as builds are still
> ongoing. However there appears to be a perf issue:
>
> https://autobuilder.yocto.io/builders/nightly-deb-non-deb/builds/429/steps/BuildImages/logs/stdio
> https://autobuilder.yocto.io/builders/nightly-packagemanagers/builds/77/steps/BuildImages/logs/stdio
> https://autobuilder.yocto.io/builders/nightly-packagemanagers/builds/77/steps/BuildImages_1/logs/stdio
> https://autobuilder.yocto.io/builders/nightly-packagemanagers/builds/77/steps/BuildImages_2/logs/stdio
> [and so on]
>

Again, I'm not going to be much good on fixing this.

I of course have built (and run perf on target) for all the
architectures or I never would have sent the pull request.

I'll see if I can find something wrong on what my building
was producing, but otherwise, I have no way to reproduce it.

Bruce

> Cheers,
>
> Richard
>
>
>