Bruce, Yocto kernel folks:

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

This release moves onto monitoring the v5.4.x content since the v5.3.18
kernel was the last in the v5.3.x series.  As the v5.4.5 was released at
the same time as v5.3.18, the content monitoring here starts with the
v5.4.6 release, resulting in just over 60 commits here for v5.2.32.

Normally, I'd consider adding additional content from the next candidate
but as the v5.4.7 release has a hefty 433 commits(!) to consider, I
decided against doing that, and just went with the smaller release here.

I've put this 5.2.32 queue through the usual 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.

I did the signed tag just as per the previously released versions.
Please find a signed v5.2.32 tag using this key:

http://pgp.mit.edu/pks/lookup?op=vindex&search=0xEBCE84042C07D1D6

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 (#8385): 
https://lists.yoctoproject.org/g/linux-yocto/message/8385
Mute This Topic: https://lists.yoctoproject.org/mt/71166223/21656
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub  
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to