From: bruce.ashfield@gmail.com
To: steve@sakoman.com
Cc: openembedded-core@lists.openembedded.org
Subject: [OE-core][kirkstone 0/5] kirkstone: kerne updates
Date: Fri, 6 Sep 2024 14:02:42 -0400 [thread overview]
Message-ID: <20240906180247.376758-1-bruce.ashfield@gmail.com> (raw)
From: Bruce Ashfield <bruce.ashfield@gmail.com>
Steve,
Discard any old -stable bumps that I have previously sent.
These contain all of that content and should fix the configuration
warning you were seeing on the last set of bumps.
As usual, let me know if there are issues and I'll fix them up.
Bruce
Bruce Ashfield (5):
linux-yocto/5.10: update to v5.10.216
linux-yocto/5.10: remove obsolete options
linux-yocto/5.10: update to v5.10.223
linux-yocto/5.15: update to v5.15.165
linux-yocto/5.15: update to v5.15.166
.../linux/linux-yocto-rt_5.10.bb | 6 ++---
.../linux/linux-yocto-rt_5.15.bb | 6 ++---
.../linux/linux-yocto-tiny_5.10.bb | 8 +++---
.../linux/linux-yocto-tiny_5.15.bb | 6 ++---
meta/recipes-kernel/linux/linux-yocto_5.10.bb | 24 ++++++++---------
meta/recipes-kernel/linux/linux-yocto_5.15.bb | 26 +++++++++----------
6 files changed, 38 insertions(+), 38 deletions(-)
--
2.39.2
next reply other threads:[~2024-09-06 18:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-06 18:02 bruce.ashfield [this message]
2024-09-06 18:02 ` [OE-core][kirkstone 1/5] linux-yocto/5.10: update to v5.10.216 bruce.ashfield
2024-09-06 18:02 ` [OE-core][kirkstone 2/5] linux-yocto/5.10: remove obsolete options bruce.ashfield
2024-09-06 18:02 ` [OE-core][kirkstone 3/5] linux-yocto/5.10: update to v5.10.223 bruce.ashfield
2024-09-10 13:10 ` Steve Sakoman
2024-09-10 13:38 ` Bruce Ashfield
2024-09-10 14:19 ` Steve Sakoman
2024-09-06 18:02 ` [OE-core][kirkstone 4/5] linux-yocto/5.15: update to v5.15.165 bruce.ashfield
2024-09-06 18:02 ` [OE-core][kirkstone 5/5] linux-yocto/5.15: update to v5.15.166 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=20240906180247.376758-1-bruce.ashfield@gmail.com \
--to=bruce.ashfield@gmail.com \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox