From: bruce.ashfield@gmail.com
To: steve@sakoman.com, richard.purdie@linuxfoundation.org
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/5] [dunfell]: kernel: -stable updates
Date: Mon, 20 Dec 2021 10:12:14 -0500 [thread overview]
Message-ID: <cover.1640012653.git.bruce.ashfield@gmail.com> (raw)
From: Bruce Ashfield <bruce.ashfield@gmail.com>
Steve,
I thought I had sent some of these before, but I didn't notice them
in any of the recent dunfell updates.
Here are the tested -stable updates that I've done (hence they aren't
squashed, since each set of SRCREVs are a useful test/debug point).
Cheers,
Bruce
The following changes since commit 795339092f87672e4f68e4d3bc4cfd0e252d1831:
build-appliance-image: Update to dunfell head revision (2021-12-14 22:49:36 +0000)
are available in the Git repository at:
git://git.yoctoproject.org/poky-contrib zedd/kernel-dunfell
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel-dunfell
Bruce Ashfield (5):
linux-yocto/5.4: update to v5.4.159
linux-yocto/5.4: update to v5.4.162
linux-yocto/5.4: update to v5.4.163
linux-yocto/5.4: update to v5.4.165
linux-yocto/5.4: update to v5.4.167
.../linux/linux-yocto-rt_5.4.bb | 6 ++---
.../linux/linux-yocto-tiny_5.4.bb | 8 +++----
meta/recipes-kernel/linux/linux-yocto_5.4.bb | 22 +++++++++----------
3 files changed, 18 insertions(+), 18 deletions(-)
--
2.19.1
next reply other threads:[~2021-12-20 15:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-20 15:12 bruce.ashfield [this message]
2021-12-20 15:12 ` [PATCH 1/5] linux-yocto/5.4: update to v5.4.159 bruce.ashfield
2021-12-20 15:12 ` [PATCH 2/5] linux-yocto/5.4: update to v5.4.162 Bruce Ashfield
2021-12-20 15:12 ` [PATCH 3/5] linux-yocto/5.4: update to v5.4.163 bruce.ashfield
2021-12-20 15:12 ` [PATCH 4/5] linux-yocto/5.4: update to v5.4.165 bruce.ashfield
2021-12-20 15:12 ` [PATCH 5/5] linux-yocto/5.4: update to v5.4.167 bruce.ashfield
2021-12-20 15:15 ` [PATCH 0/5] [dunfell]: kernel: -stable updates Steve Sakoman
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.1640012653.git.bruce.ashfield@gmail.com \
--to=bruce.ashfield@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=steve@sakoman.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.