Bruce, Yocto kernel folks:

Here is the next 5.2.x stable update "extension" primarily created for
the Yocto project, as the next v5.2.x post-EOL release.

The content is from an audit of what went into the v5.4.22 to v5.4.24
releases - plus any upstream commits listed as Fixes: for backports in
the above v5.4.x content, and a few upstream commits for recent CVE.

There are just over 540 commits deployed here that were applicable for
this v5.2.40 release, perhaps the largest yet?  Seems to be the trend..

KVM had ~20 so I did an extra sanity test with v5.2.40-defconfig plus KVM
options enabled and used the same kernel binary as host and as the guest
kernel on an older Xeon E5530 COTS platform, and things seemed as normal.

I've also put this 5.2.40 queue through the normal testing; build
testing on x86-64/32, ARM-64/32, PPC and MIPS, plus some static analysis
and finally some sanity runtime tests on x86-64.

Please find tag v5.2.40 (a45fc60d807e224eea2aae5690b87f946ae13bbb) as
the current head of linux-5.2.y branch in the repo in the kernel.org
directory here:

  
https://git.kernel.org/pub/scm/linux/kernel/git/paulg/linux-5.2.y.git/?h=linux-5.2.y
  git://git.kernel.org/pub/scm/linux/kernel/git/paulg/linux-5.2.y.git

for merge to standard/base in linux-yocto-5.2 and then out from there
into the other base and BSP branches.

For those who are interested, the evolution of the commits is here:

  https://git.kernel.org/cgit/linux/kernel/git/paulg/longterm-queue-5.2.git/

This repo isn't needed for anything; it just exists for transparency and
so people can see the evolution of the raw commits that were originally
selected to create this 5.2.x release.

Paul.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#8672): 
https://lists.yoctoproject.org/g/linux-yocto/message/8672
Mute This Topic: https://lists.yoctoproject.org/mt/74326837/21656
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub  
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to