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

There is one trivial one line commit to fix a build error on PPC64 from
the MDS patches of v4.18.37 - which was also present in GregKH's stable
releases our v4.18.37 was based on.  That patch is 1st in the queue if
anyone is looking for it.  Greg also has the fix now, and so fingers
crossed that we don't see any more whole releases for a single bug-fix
for months and months.  

There are about 165 commits here, based on commits chosen from what were
used in the 4.19.37 and 4.19.38 stable releases.  I had most of this
work done before MDS came along, hence the close together releases.

There is a slight bias towards networking in the content here; it seems
in v4.19, an ipv6 frag issue was best resolved by importing work that
combined some ipv4/ipv6 code first.  And for 4.18 here, I had to extend
that slightly by getting some related commits between 4.18 and 4.19.
But after doing that, the related commits played nice together during
application, and some basic ping6 tests didn't reveal any issues.

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.38 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