From: bruce.ashfield@gmail.com
To: richard.purdie@linuxfoundation.org
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH 00/12] kernel-yocto: consolidated pull request
Date: Wed, 8 Nov 2023 09:16:18 -0500 [thread overview]
Message-ID: <cover.1699452828.git.bruce.ashfield@gmail.com> (raw)
From: Bruce Ashfield <bruce.ashfield@gmail.com>
Richard,
Here's the latest set of kernel changes. There's more tools changes
than normal, but I don't expect issues.
Otherwise, this is mainly -stable bumps, as I prepare to move the
-dev kernel to the latest.
Bruce
The following changes since commit 832384fdc69bd909183da7572ab8171dc34542c3:
poky-tiny: fix PACKAGE_EXCLUDE (2023-11-08 11:00:09 +0000)
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 (12):
linux-yocto/6.5: update to v6.5.8
linux-yocto/6.1: update to v6.1.59
linux-yocto/6.5: update to v6.5.9
linux-yocto/6.1: update to v6.1.60
kern-tools: make lower context patches reproducible
kern-tools: bump SRCREV for queue processing changes
kern-tools: update SRCREV to include SECURITY.md file
kernel-yocto: improve metadata patching
linux-yocto/6.1: cfg: restore CONFIG_DEVMEM
linux-yocto/6.5: cfg: restore CONFIG_DEVMEM
linux-yocto/6.5: update to v6.5.10
linux-yocto/6.1: update to v6.1.61
meta/classes-recipe/kernel-yocto.bbclass | 30 +++++++++++++++----
.../kern-tools/kern-tools-native_git.bb | 2 +-
.../linux/linux-yocto-rt_6.1.bb | 6 ++--
.../linux/linux-yocto-rt_6.5.bb | 6 ++--
.../linux/linux-yocto-tiny_6.1.bb | 6 ++--
.../linux/linux-yocto-tiny_6.5.bb | 6 ++--
meta/recipes-kernel/linux/linux-yocto_6.1.bb | 28 ++++++++---------
meta/recipes-kernel/linux/linux-yocto_6.5.bb | 28 ++++++++---------
8 files changed, 66 insertions(+), 46 deletions(-)
--
2.34.1
next reply other threads:[~2023-11-08 14:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-08 14:16 bruce.ashfield [this message]
2023-11-08 14:16 ` [PATCH 01/12] linux-yocto/6.5: update to v6.5.8 bruce.ashfield
2023-11-08 14:16 ` [PATCH 02/12] linux-yocto/6.1: update to v6.1.59 bruce.ashfield
2023-11-08 14:16 ` [PATCH 03/12] linux-yocto/6.5: update to v6.5.9 bruce.ashfield
2023-11-08 14:16 ` [PATCH 04/12] linux-yocto/6.1: update to v6.1.60 bruce.ashfield
2023-11-08 14:16 ` [PATCH 05/12] kern-tools: make lower context patches reproducible bruce.ashfield
2023-11-08 14:16 ` [PATCH 06/12] kern-tools: bump SRCREV for queue processing changes bruce.ashfield
2023-11-08 14:16 ` [PATCH 07/12] kern-tools: update SRCREV to include SECURITY.md file bruce.ashfield
2023-11-08 14:16 ` [PATCH 08/12] kernel-yocto: improve metadata patching bruce.ashfield
2023-11-08 14:16 ` [PATCH 09/12] linux-yocto/6.1: cfg: restore CONFIG_DEVMEM bruce.ashfield
2023-11-08 14:16 ` [PATCH 10/12] linux-yocto/6.5: " bruce.ashfield
2023-11-08 14:16 ` [PATCH 11/12] linux-yocto/6.5: update to v6.5.10 bruce.ashfield
2023-11-08 14:16 ` [PATCH 12/12] linux-yocto/6.1: update to v6.1.61 bruce.ashfield
-- strict thread matches above, loose matches on Subject: below --
2018-01-26 13:59 [PATCH 00/12] kernel-yocto: consolidated pull request 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.1699452828.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