From: bruce.ashfield@gmail.com
To: richard.purdie@linuxfoundation.org
Cc: openembedded-core@lists.openembedded.org, haokexin@gmail.com
Subject: [PATCH 0/7] linux-yocto: consolidated pull request
Date: Tue, 6 Jan 2026 10:23:45 -0500 [thread overview]
Message-ID: <20260106152352.932717-1-bruce.ashfield@gmail.com> (raw)
From: Bruce Ashfield <bruce.ashfield@gmail.com>
Hi all,
I'm still tweaking my pull request scripts for the split repositories,
so apologies if something doesn't look quite right.
I'm unable to push to openembedded-contrib right now, so this is a
patch only send.
We are getting closer to removing 6.16 (and then 6.12) from oe-core
master. These updates should address some config warnings, and
otherwise improve stability.
We need to get the reference platforms update to 6.18, so I've cc'
kevin@windriver to see if he has any plans or comments on that.
Cheers,
Bruce
OE-core (7):
linux-yocto/6.18: genericarm64: remove SLIM_QCOM_CTR
linux-yocto/6.12: update to v6.12.63
linux-yocto/6.12: update CVE exclusions (6.12.63)
linux-yocto/6.18: libpf prepare for new glibc
linux-yocto/6.18: update to v6.18.3
linux-yocto/6.18: update CVE exclusions (6.18.3)
linux-yocto/6.18: mtd: use refcount to prevent corruption
OE-core:
meta/recipes-kernel/linux/cve-exclusion_6.12.inc | 380 +-
meta/recipes-kernel/linux/cve-exclusion_6.18.inc | 12024 +++++++++++--------
meta/recipes-kernel/linux/linux-yocto-rt_6.12.bb | 6 +-
meta/recipes-kernel/linux/linux-yocto-rt_6.18.bb | 6 +-
meta/recipes-kernel/linux/linux-yocto-tiny_6.12.bb | 6 +-
meta/recipes-kernel/linux/linux-yocto-tiny_6.18.bb | 6 +-
meta/recipes-kernel/linux/linux-yocto_6.12.bb | 28 +-
meta/recipes-kernel/linux/linux-yocto_6.18.bb | 24 +-
8 files changed, 7168 insertions(+), 5312 deletions(-)
--
2.39.2
next reply other threads:[~2026-01-06 15:24 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-06 15:23 bruce.ashfield [this message]
2026-01-06 15:23 ` [meta][PATCH 01/07] linux-yocto/6.18: genericarm64: remove SLIM_QCOM_CTR bruce.ashfield
2026-01-06 15:23 ` [meta][PATCH 02/07] linux-yocto/6.12: update to v6.12.63 bruce.ashfield
2026-01-06 15:23 ` [meta][PATCH 03/07] linux-yocto/6.12: update CVE exclusions (6.12.63) bruce.ashfield
2026-01-06 15:23 ` [meta][PATCH 04/07] linux-yocto/6.18: libpf prepare for new glibc bruce.ashfield
2026-01-06 15:23 ` [meta][PATCH 05/07] linux-yocto/6.18: update to v6.18.3 bruce.ashfield
2026-01-06 15:23 ` [meta][PATCH 07/07] linux-yocto/6.18: mtd: use refcount to prevent corruption bruce.ashfield
2026-01-07 12:53 ` [PATCH 0/7] linux-yocto: consolidated pull request Kevin Hao
2026-01-07 13:59 ` Bruce Ashfield
-- strict thread matches above, loose matches on Subject: below --
2023-12-21 14:25 bruce.ashfield
2023-12-05 4:26 bruce.ashfield
2022-06-07 13:59 bruce.ashfield
2020-10-06 19:04 Bruce Ashfield
2018-05-18 15:05 Bruce Ashfield
2018-03-27 15:03 Bruce Ashfield
2018-03-28 10:31 ` Burton, Ross
2018-03-28 10:33 ` Burton, Ross
2018-03-28 12:01 ` Bruce Ashfield
2018-03-28 12:07 ` Burton, Ross
2018-03-28 12:57 ` Bruce Ashfield
2018-03-29 12:58 ` Bruce Ashfield
2018-03-29 13:13 ` Richard Purdie
2018-03-29 13:55 ` Bruce Ashfield
2016-11-22 15:58 Bruce Ashfield
2015-05-21 19:08 Bruce Ashfield
2014-09-23 14:57 Bruce Ashfield
2014-09-08 19:55 [PATCH 0/7] linux-yocto*: " Bruce Ashfield
2014-09-09 11:42 ` Burton, Ross
2014-09-09 12:55 ` 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=20260106152352.932717-1-bruce.ashfield@gmail.com \
--to=bruce.ashfield@gmail.com \
--cc=haokexin@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