Bruce, Yocto kernel folks: Here is the next 4.18.x stable update "extension" primarily created for the Yocto project, continuing from the previous v4.18.35 release.
There are just over 185 commits here, based on commits chosen from what was used in the 4.19.35 and 4.19.36 stable releases. I'd incorrectly stated in the previous release announcement that 4.18.35 was based on 4.19.33; rather it was based on 4.19.34 content. Too many version numbers all close together... in any case the full history of the sourced and altered commits can be found in the 2nd repo below. Again there is no one stand out feature with a bunch of fixes applied; they seem fairly uniformly spread out over the tree. I've put this 4.18.x 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 expect to be doing similar updates for approximately another four months - but it is never to early for users to start thinking ahead. I did the signed tag just as per the previously released versions. Please find a signed v4.18.36 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-4.18.y.git/?h=linux-4.18.y git://git.kernel.org/pub/scm/linux/kernel/git/paulg/linux-4.18.y.git for merge to standard/base in linux-yocto-4.18 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-4.18.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 4.18.x release. Paul. -- _______________________________________________ linux-yocto mailing list [email protected] https://lists.yoctoproject.org/listinfo/linux-yocto
