From: bruce.ashfield@gmail.com
To: richard.purdie@linuxfoundation.org
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/9] linux-yocto: consolidated (-stable) pull request
Date: Wed, 18 Dec 2019 09:07:25 -0500 [thread overview]
Message-ID: <cover.1576677592.git.bruce.ashfield@gmail.com> (raw)
From: Bruce Ashfield <bruce.ashfield@gmail.com>
Hi all,
Here is a delayed pull request on -stable updates that I've had queued
for a while now.
I had put a goal to test all of these on the autobuilder before sending
them, and we did manage to get that done. I've run the quick config against
both the 5.2 and 4.19 updates.
I have almost as many pending commits for the -stable updates queued, but
wanted to get these out first. As usual, the distict commits are on
purpose, since they represent known good build + boot test points.
Also, I hope to have 5.4 as the versioned kernel (dropping 5.2 and 4.19)
in master shortly, but the mips64 boot issue is still persisting and
needs to be solved.
Let's see if the AB testing I did was enough .. or something else manages
to pop out during integration builds!
Cheers,
Bruce
The following changes since commit 7e7b066085c2496a259b356c59acda32d444a261:
YP 3.1 Docs: Updated Manual revision tables. (2019-12-16 23:32:33 +0000)
are available in the Git repository at:
git://git.pokylinux.org/poky-contrib zedd/kernel
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
Bruce Ashfield (9):
linux-yocto-dev: bump to v5.4+
linux-yocto/5.2: update to v5.2.21
linux-yocto/5.2: update to v5.2.22
linux-yocto/5.2: update to v5.2.23
linux-yocto/4.19: update to v4.19.84
linux-yocto/5.2: update to v5.2.24
linux-yocto/4.19: update to v4.19.87
linux-yocto/5.2: update to v5.2.25
linux-yocto/5.2: update to v5.2.26
meta/recipes-kernel/linux/linux-yocto-dev.bb | 2 +-
.../linux/linux-yocto-rt_4.19.bb | 6 ++---
.../linux/linux-yocto-rt_5.2.bb | 6 ++---
.../linux/linux-yocto-tiny_4.19.bb | 8 +++----
.../linux/linux-yocto-tiny_5.2.bb | 8 +++----
meta/recipes-kernel/linux/linux-yocto_4.19.bb | 20 ++++++++---------
meta/recipes-kernel/linux/linux-yocto_5.2.bb | 22 +++++++++----------
7 files changed, 36 insertions(+), 36 deletions(-)
--
2.19.1
next reply other threads:[~2019-12-18 14:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-18 14:07 bruce.ashfield [this message]
2019-12-18 14:07 ` [PATCH 1/9] linux-yocto-dev: bump to v5.4+ bruce.ashfield
2019-12-18 19:11 ` akuster808
2019-12-18 19:48 ` Bruce Ashfield
2019-12-18 20:07 ` akuster808
2019-12-18 21:02 ` Bruce Ashfield
2019-12-18 14:07 ` [PATCH 2/9] linux-yocto/5.2: update to v5.2.21 bruce.ashfield
2019-12-18 14:07 ` [PATCH 3/9] linux-yocto/5.2: update to v5.2.22 bruce.ashfield
2019-12-18 14:07 ` [PATCH 4/9] linux-yocto/5.2: update to v5.2.23 bruce.ashfield
2019-12-18 14:07 ` [PATCH 5/9] linux-yocto/4.19: update to v4.19.84 bruce.ashfield
2019-12-18 14:07 ` [PATCH 6/9] linux-yocto/5.2: update to v5.2.24 bruce.ashfield
2019-12-18 14:07 ` [PATCH 7/9] linux-yocto/4.19: update to v4.19.87 bruce.ashfield
2019-12-18 14:07 ` [PATCH 8/9] linux-yocto/5.2: update to v5.2.25 bruce.ashfield
2019-12-18 14:07 ` [PATCH 9/9] linux-yocto/5.2: update to v5.2.26 bruce.ashfield
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1576677592.git.bruce.ashfield@gmail.com \
--to=bruce.ashfield@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox