From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/3] linux-yocto: consolidated pull request
Date: Sat, 12 Jan 2019 13:12:50 -0500 [thread overview]
Message-ID: <cover.1547316462.git.bruce.ashfield@windriver.com> (raw)
Hi all,
Here's the next batch of kernel updates. Nothing particular of note, but we
do gain new BSP descriptions for qemuarma15 and qemuriscv64. Although the
full machine definitions are not in oe-core yet, this sets the table for them
to be made widely available.
Other than that, I bumped the -dev kernel to 5.x, and have pulled in the
latest round of -stable updates to 4.19 (also note that I updated 4.14
with -stable updates as well, but haven't done the older branch SRCREVs
yet).
Cheers,
Bruce
The following changes since commit 46f6f6a5f9de5e7f8f32f6ae768af61ec20ade4a:
bitbake: bitbake: runqueue: Use multiconfig name to fetch unihash (2019-01-11 10:39:30 +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 (3):
linux-yocto/4.19: introduce qemuriscv64 and qemuarma15 BSP definitions
linux-yocto/4.19: update to v4.19.14
linux-yocto-dev: bump to v5.0-rc
meta/recipes-kernel/linux/linux-yocto-dev.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto-rt_4.19.bb | 6 +++---
meta/recipes-kernel/linux/linux-yocto-tiny_4.19.bb | 8 ++++----
meta/recipes-kernel/linux/linux-yocto_4.19.bb | 20 ++++++++++----------
4 files changed, 18 insertions(+), 18 deletions(-)
--
2.5.0
next reply other threads:[~2019-01-12 18:13 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-12 18:12 Bruce Ashfield [this message]
2019-01-12 18:12 ` [PATCH 1/3] linux-yocto/4.19: introduce qemuriscv64 and qemuarma15 BSP definitions Bruce Ashfield
2019-01-12 18:34 ` Khem Raj
2019-01-12 18:44 ` Bruce Ashfield
2019-01-12 20:17 ` Khem Raj
2019-01-13 17:24 ` Alistair Francis
2019-01-13 18:30 ` Khem Raj
2019-01-12 18:12 ` [PATCH 2/3] linux-yocto/4.19: update to v4.19.14 Bruce Ashfield
2019-01-12 18:12 ` [PATCH 3/3] linux-yocto-dev: bump to v5.0-rc Bruce Ashfield
-- strict thread matches above, loose matches on Subject: below --
2020-03-22 1:18 [PATCH 0/3] linux-yocto: consolidated pull request Bruce Ashfield
2019-02-09 18:37 bruce.ashfield
2019-02-06 19:50 bruce.ashfield
2019-01-21 17:26 Bruce Ashfield
2018-04-09 15:16 Bruce Ashfield
2016-09-20 15:16 Bruce Ashfield
2016-06-06 8:15 Bruce Ashfield
2016-05-24 15:53 Bruce Ashfield
2013-11-26 17:33 Bruce Ashfield
2013-09-18 18:24 Bruce Ashfield
2012-12-03 20:49 Bruce Ashfield
2012-08-27 4:49 Bruce Ashfield
2012-08-28 14:22 ` Saul Wold
2012-08-29 7:58 ` Bruce Ashfield
2012-03-05 4:01 Bruce Ashfield
2012-03-13 15:54 ` Saul Wold
2012-02-27 19:34 Bruce Ashfield
2012-02-28 18:41 ` Saul Wold
2012-01-04 20:12 Bruce Ashfield
2011-12-08 17:11 Bruce Ashfield
2011-09-14 18:11 Bruce Ashfield
2011-09-15 17:37 ` Saul Wold
2011-09-03 3:03 Bruce Ashfield
2011-09-05 19:26 ` Richard Purdie
2011-08-19 5:20 Bruce Ashfield
2011-08-20 5:08 ` Bruce Ashfield
2011-08-15 20:24 Bruce Ashfield
2011-08-22 22:37 ` Saul Wold
2011-05-09 18:34 Bruce Ashfield
2011-05-10 17:53 ` Saul Wold
2011-05-05 4:53 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.1547316462.git.bruce.ashfield@windriver.com \
--to=bruce.ashfield@windriver.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