From: bruce.ashfield@gmail.com
To: richard.purdie@linuxfoundation.org
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/6] kernel-yocto: consolidated pull request
Date: Tue, 6 May 2025 12:32:54 -0400 [thread overview]
Message-ID: <cover.1746548780.git.bruce.ashfield@gmail.com> (raw)
From: Bruce Ashfield <bruce.ashfield@gmail.com>
Hi Richard,
Now that I'm back at my desk, here are the queued -stable, configuration
and feature changes that I have queued.
I'll be sending -stable updates to the LTS branches as well.
Note: once patch #1 is in the tree and doesn't need any more tweaks, I'll
send a documenation update. This is the patch that we need to enable the
modular initrd work in kernel-yocto references.
Cheers,
Bruce
The following changes since commit 601b05a298c0847e96b8f5f71e50d057e2833382:
mesa: Fix header search paths (2025-05-05 18:02:48 +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 (6):
kernel-yocto: allow annotated options to be modified
linux-yocto-dev: update to v6.15
linux-yocto/6.12: update to v6.12.24
linux-yocto/6.12: update to v6.12.25
linux-yocto/6.12: bsp/genericarm64: modular configuration updates
linux-yocto/6.12: update to v6.12.27
meta/classes-recipe/kernel-yocto.bbclass | 7 ++++-
.../kern-tools/kern-tools-native_git.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto-dev.bb | 4 +--
.../linux/linux-yocto-rt_6.12.bb | 6 ++--
.../linux/linux-yocto-tiny_6.12.bb | 6 ++--
meta/recipes-kernel/linux/linux-yocto_6.12.bb | 28 +++++++++----------
6 files changed, 29 insertions(+), 24 deletions(-)
--
2.39.2
next reply other threads:[~2025-05-06 16:33 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-06 16:32 bruce.ashfield [this message]
2025-05-06 16:32 ` [PATCH 1/6] kernel-yocto: allow annotated options to be modified bruce.ashfield
2025-05-06 16:32 ` [PATCH 2/6] linux-yocto-dev: update to v6.15 bruce.ashfield
2025-05-06 16:32 ` [PATCH 3/6] linux-yocto/6.12: update to v6.12.24 bruce.ashfield
2025-05-06 16:32 ` [PATCH 4/6] linux-yocto/6.12: update to v6.12.25 bruce.ashfield
2025-05-06 16:32 ` [PATCH 5/6] linux-yocto/6.12: bsp/genericarm64: modular configuration updates bruce.ashfield
2025-05-06 16:33 ` [PATCH 6/6] linux-yocto/6.12: update to v6.12.27 bruce.ashfield
2025-05-07 7:42 ` [OE-core] [PATCH 0/6] kernel-yocto: consolidated pull request Mathieu Dubois-Briand
2025-05-07 7:58 ` Richard Purdie
[not found] ` <183D2FC291E34522.16348@lists.openembedded.org>
2025-05-07 11:18 ` Richard Purdie
2025-05-07 11:39 ` Mikko Rapeli
2025-05-07 13:03 ` Bruce Ashfield
2025-05-15 16:06 ` Fabio Estevam
-- strict thread matches above, loose matches on Subject: below --
2025-07-08 14:36 bruce.ashfield
2025-07-09 7:58 ` Richard Purdie
2025-07-09 13:01 ` Bruce Ashfield
2024-12-10 21:06 bruce.ashfield
2024-11-21 4:13 bruce.ashfield
2024-11-21 16:50 ` Richard Purdie
2022-04-04 15:19 bruce.ashfield
2021-07-29 4:49 Bruce Ashfield
2021-06-16 20:48 Bruce Ashfield
2017-07-11 15:04 Bruce Ashfield
2017-06-08 19:21 Bruce Ashfield
2016-08-15 18:26 Bruce Ashfield
2016-08-16 16:00 ` Burton, Ross
2016-08-16 16:01 ` Bruce Ashfield
2016-08-16 16:10 ` Burton, Ross
2016-08-16 16:11 ` Bruce Ashfield
2016-08-16 16:15 ` Burton, Ross
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.1746548780.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox