From: bruce.ashfield@gmail.com
To: richard.purdie@linuxfoundation.org
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH 00/11] kernel-yocto: -stable, -dev and tools
Date: Wed, 15 Oct 2025 23:08:33 -0400 [thread overview]
Message-ID: <cover.1760583881.git.bruce.ashfield@gmail.com> (raw)
From: Bruce Ashfield <bruce.ashfield@gmail.com>
Richard,
I realize we are still fighting the perf reproducibility issues, but
I wanted to send these out since there have been some questions about
-stable, 6.18+ and configuration issues.
Plus I was able to get these patches off my machine with hardware issues,
so I wanted to get them sent.
Feel free to disregard any of the patches that we don't want, they'll
be on the list for anyone looking for them.
The -stable updates are routine, 6.18+ won't impact existing release
kernels, and the configuration updates for genericarm64 are additive.
So the risk is low for the series as a whole.
Cheers,
Bruce
The following changes since commit 64a879e9b61b56e8bd8070b3f906d9d35fc4153d:
perf: Bump versions to resolve hashequiv/reproducibility issues (2025-10-15 17:15:46 +0100)
are available in the Git repository at:
https://git.yoctoproject.org/poky-contrib zedd/kernel
https://git.yoctoproject.org/poky-contrib/log/?h=zedd/kernel
Bruce Ashfield (11):
linux-yocto/6.16: update to v6.16.11
linux-yocto/6.16: update CVE exclusions (6.16.11)
linux-yocto/6.12: update to v6.12.50
linux-yocto/6.12: update CVE exclusions (6.12.50)
linux-yocto/6.12: update to v6.12.51
linux-yocto/6.12: update CVE exclusions (6.12.51)
linux-yocto/6.12: update to v6.12.52
linux-yocto/6.12: update CVE exclusions (6.12.52)
linux-yocto/6.16: genericarm64: feature splits and enablement
kern-tools: fix symbol_why for v6.18-rc1+
linux-yocto-dev: update to v6.18
.../kern-tools/kern-tools-native_git.bb | 2 +-
.../linux/cve-exclusion_6.12.inc | 966 +++++++++++++++++-
.../linux/cve-exclusion_6.16.inc | 658 +++++++++++-
meta/recipes-kernel/linux/linux-yocto-dev.bb | 4 +-
.../linux/linux-yocto-rt_6.12.bb | 6 +-
.../linux/linux-yocto-rt_6.16.bb | 6 +-
.../linux/linux-yocto-tiny_6.12.bb | 6 +-
.../linux/linux-yocto-tiny_6.16.bb | 6 +-
meta/recipes-kernel/linux/linux-yocto_6.12.bb | 28 +-
meta/recipes-kernel/linux/linux-yocto_6.16.bb | 28 +-
10 files changed, 1607 insertions(+), 103 deletions(-)
--
2.39.2
next reply other threads:[~2025-10-16 3:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-16 3:08 bruce.ashfield [this message]
2025-10-16 3:08 ` [PATCH 01/11] linux-yocto/6.16: update to v6.16.11 bruce.ashfield
2025-10-16 3:08 ` [PATCH 02/11] linux-yocto/6.16: update CVE exclusions (6.16.11) bruce.ashfield
2025-10-16 3:08 ` [PATCH 03/11] linux-yocto/6.12: update to v6.12.50 bruce.ashfield
2025-10-16 3:08 ` [PATCH 04/11] linux-yocto/6.12: update CVE exclusions (6.12.50) bruce.ashfield
2025-10-16 3:08 ` [PATCH 05/11] linux-yocto/6.12: update to v6.12.51 bruce.ashfield
2025-10-16 3:08 ` [PATCH 06/11] linux-yocto/6.12: update CVE exclusions (6.12.51) bruce.ashfield
2025-10-16 3:08 ` [PATCH 07/11] linux-yocto/6.12: update to v6.12.52 bruce.ashfield
2025-10-16 3:08 ` [PATCH 08/11] linux-yocto/6.12: update CVE exclusions (6.12.52) bruce.ashfield
2025-10-16 3:08 ` [PATCH 09/11] linux-yocto/6.16: genericarm64: feature splits and enablement bruce.ashfield
2025-10-16 3:08 ` [PATCH 10/11] kern-tools: fix symbol_why for v6.18-rc1+ bruce.ashfield
2025-10-16 3:08 ` [PATCH 11/11] linux-yocto-dev: update to v6.18 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.1760583881.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 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.