On Wed, Mar 27, 2019 at 9:34 AM Paul Gortmaker <paul.gortma...@windriver.com> wrote: > > 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.32 release. > > There are about 260 commits here, based on commits chosen from what > was used in the recent 4.19.31 stable release. So, yes, another > bigger one, but still no one big feature/area was responsible. > > 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.33 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 >
Merged. I had a minor conflict on the -rt branches, but looking at 4.19-rt my resolution of it should be consistent with what upstream did as well. Worth double checking and sending me a fixup patch if I did mess it up. Bruce > 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. -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II -- _______________________________________________ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto