From: "Bruce Ashfield" <bruce.ashfield@gmail.com>
To: richard.purdie@linuxfoundation.org
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/4] linux-yocto: -stable and -dev updates
Date: Mon, 31 May 2021 09:16:42 -0400 [thread overview]
Message-ID: <cover.1622466879.git.bruce.ashfield@gmail.com> (raw)
From: Bruce Ashfield <bruce.ashfield@gmail.com>
Richard,
-rc4 has rolled in for 5.13, which is about the time that I normally make
it the -dev kernel version. I've been testing it locally since -rc1, so
it is good to go.
So we bump that version, as well as grab the latest -stable kernel updates
for the active versions.
Cheers,
Bruce
The following changes since commit 40d3366bea8d2417e89a37c6f2d38e1542160342:
flex: correct license information (2021-05-28 06:41:03 +0100)
are available in the Git repository at:
git://git.yoctoproject.org/poky-contrib zedd/kernel
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
Bruce Ashfield (4):
linux-yocto-dev: bump to v5.13+
linux-yocto/5.4: update to v5.4.120
linux-yocto/5.10: update to v5.10.41
linux-yocto/5.4: update to v5.4.123
meta/recipes-kernel/linux/linux-yocto-dev.bb | 2 +-
.../linux/linux-yocto-rt_5.10.bb | 6 ++---
.../linux/linux-yocto-rt_5.4.bb | 6 ++---
.../linux/linux-yocto-tiny_5.10.bb | 8 +++----
.../linux/linux-yocto-tiny_5.4.bb | 8 +++----
meta/recipes-kernel/linux/linux-yocto_5.10.bb | 24 +++++++++----------
meta/recipes-kernel/linux/linux-yocto_5.4.bb | 22 ++++++++---------
7 files changed, 38 insertions(+), 38 deletions(-)
--
2.19.1
next reply other threads:[~2021-05-31 13:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-31 13:16 Bruce Ashfield [this message]
2021-05-31 13:16 ` [PATCH 1/4] linux-yocto-dev: bump to v5.13+ Bruce Ashfield
2021-05-31 13:16 ` [PATCH 2/4] linux-yocto/5.4: update to v5.4.120 Bruce Ashfield
2021-05-31 13:16 ` [PATCH 3/4] linux-yocto/5.10: update to v5.10.41 Bruce Ashfield
2021-05-31 13:16 ` [PATCH 4/4] linux-yocto/5.4: update to v5.4.123 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.1622466879.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