[linux-yocto] v4.18.x - stable updates comprising v4.18.26

[Paul Gortmaker]

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

This release is slightly different in terms of how the commits were
chosen.  Instead of taking references from 4.19.x *stable* releases,
these commits are chosen from analysis of 4.19 *mainline* commits.

To explain further, imagine a commit added to 4.18 mainline, which had
an issue found and fixed in the content used to make the final 4.19
mainline release.  We would never see that commit in a 4.19.x stable
release, because it was already present in what was mainline 4.19; which
could be called "v4.19.0" if that helps explain things.  If the breakage
was found and fixed *after* v4.19 mainline, like say v4.20, then it
would be considered for backporting to v4.19.x stable, and hence we
should see it in our normal monitoring of the 4.19.x stable releases.

So, this attempts to close that gap.  We look at commits that have a
"Fixes:" tag that references 4.18 content, which is also a commit that
landed in the 4.18-4.19 development. There are about 50 commits here.

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.26 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.18.y.git/
   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.