From: bruce.ashfield@gmail.com
To: richard.purdie@linuxfoundation.org
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/4] linux-yocto: stable bumps
Date: Tue, 29 Sep 2026 08:20:06 -0400 [thread overview]
Message-ID: <20260929122011.2449622-1-bruce.ashfield@gmail.com> (raw)
From: Bruce Ashfield <bruce.ashfield@gmail.com>
Hi all,
These are not intended for the release, but for after it goes
into maintenance.
I was asked to not hold these -stable updates during these
sorts of windows, so here they are.
Single series, across the two repos that need to be updated.
Bruce
openembedded-core (2):
linux-yocto/7.2: update to v7.2.8
linux-yocto/6.18: update to v6.18.54
meta-yocto (2):
yocto-bsps: update to v7.2.8
yocto-bsps: update to v6.18.54
openembedded-core:
meta/recipes-kernel/linux/linux-yocto-rt_6.18.bb | 4 ++--
meta/recipes-kernel/linux/linux-yocto-rt_7.2.bb | 6 +++---
meta/recipes-kernel/linux/linux-yocto-tiny_6.18.bb | 4 ++--
meta/recipes-kernel/linux/linux-yocto-tiny_7.2.bb | 6 +++---
meta/recipes-kernel/linux/linux-yocto_6.18.bb | 22 +++++++++++-----------
meta/recipes-kernel/linux/linux-yocto_7.2.bb | 24 ++++++++++++------------
6 files changed, 33 insertions(+), 33 deletions(-)
meta-yocto:
meta-yocto-bsp/recipes-kernel/linux/linux-yocto_6.18.bbappend | 2 +-
meta-yocto-bsp/recipes-kernel/linux/linux-yocto_7.2.bbappend | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
--
2.43.0
next reply other threads:[~2026-09-29 12:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 12:20 bruce.ashfield [this message]
2026-09-29 12:20 ` [meta][PATCH 01/04] linux-yocto/7.2: update to v7.2.8 bruce.ashfield
2026-09-29 12:20 ` [meta][PATCH 02/04] linux-yocto/6.18: update to v6.18.54 bruce.ashfield
2026-09-29 12:20 ` [meta-yocto-bsp][PATCH 03/04] yocto-bsps: update to v7.2.8 bruce.ashfield
2026-09-29 12:20 ` [meta-yocto-bsp][PATCH 04/04] yocto-bsps: update to v6.18.54 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=20260929122011.2449622-1-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