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.40 release.

There are about 220 commits here, based on commits chosen from what were
used in the 4.19.46/47 stable releases -- plus some TCP related commits
that were of interest to reach ahead and source from newer 4.19 now.
Not all the 47 content was processed here, in order to keep the release
size sane.  The remainder will be considered for the 4.18.42 release.

And as we enter August, I need to again remind people that the creation
of these 4.18 stable backport releases will be ending relatively soon,
as I'll expect to be moving to newer kernels used in newer Yocto
releases.  So people need to get their own maintenance or migration
plans in place as soon as possible, if they have not yet done so.

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 did the signed tag just as per the previously released versions.
Please find a signed v4.18.41 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
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto

Reply via email to