[linux-yocto] v4.12.x - stable updates comprising v4.12.29

[Paul Gortmaker]

Bruce, Yocto kernel folks:

Here is the final 4.12.x stable update "extension" primarily created for
the Yocto project, continuing on top of the previous v4.12.28 kernel.

After months of warning, hopefully it comes as no surprise to anyone
that this is the last 4.12.x release.

There are about 100 commits here, based on commits chosen from what
was used in existing 4.14.x stable releases.

The 4.14 versions I was auditing contained batch updates from DaveM in
the networking department, and hence that is represented significantly
here in these commits.

I've also jumped ahead and looked at what arm64 did in 4.14-stable for
the whole ssbd stuff, and did my best to drag that back kicking and
screaming to 4.12.

I've put this 4.12.x queue through the usual testing that I figured made
sense, which is in line with that listed explicitly in previous release
announcements.

Given the footprint of the ARM64/KVM changes for ssbd, I did an ARM64
allyesconfig and build tested that.  But to be clear, sanity boot
testing ARM64 guests is beyond what I have time/resources for.

Thank you all for making use of this kernel version.  It is nice to know
the work in backports gets used.  But the time has come to re-direct my
focus onto work for newer kernel versions.  I hope you can all move to a
newer version as well.

I did the signed tag just as per the previously released 4.12.x versions.

Please find a signed v4.12.29 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/cgit/linux/kernel/git/paulg/linux-4.12.y.git/
   git://git.kernel.org/pub/scm/linux/kernel/git/paulg/linux-4.12.y.git

for merge to standard/base in linux-yocto-4.12 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.12.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.12.x release.

Paul.
--