From: bruce.ashfield@gmail.com
To: richard.purdie@linuxfoundation.org
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH 00/11] linux-yocto: consolidated pull request
Date: Fri, 19 Jan 2024 16:14:08 -0500 [thread overview]
Message-ID: <cover.1705698717.git.bruce.ashfield@gmail.com> (raw)
From: Bruce Ashfield <bruce.ashfield@gmail.com>
Richard,
Here's the colllected -stable updates for 6.6 and 6.1. This will probably be
the last round of 6.1 updates for master, since I'll drop it shortly in
preparation for the release. 6.1 will of course continue to be updated in
linux-yocto and in older releases.
I've also reenabled my CVE update script, if any of those commits don't look
right, feel free to toss them out.
Cheers,
Bruce
The following changes since commit 7af374c90c349af2c7ae9cf7d4fa14eeeb23b108:
build-appliance-image: Update to master head revision (2024-01-19 12:22:58 +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 (11):
linux-yocto/6.6: update to v6.6.11
linux-yocto/6.6: update CVE exclusions
linux-yocto/6.1: update to v6.1.72
linux-yocto/6.1: update CVE exclusions
linux-yocto/6.6: cfg: arm: introduce page size fragments
linux-yocto/6.6: security/cfg: add configs to harden protection
linux-yocto/6.1: security/cfg: add configs to harden protection
linux-yocto/6.6: update to v6.6.12
linux-yocto/6.6: update CVE exclusions
linux-yocto/6.1: update to v6.1.73
linux-yocto/6.1: update CVE exclusions
.../linux/cve-exclusion_6.1.inc | 34 +++++++++++++++----
.../linux/cve-exclusion_6.6.inc | 30 +++++++++++++---
.../linux/linux-yocto-rt_6.1.bb | 6 ++--
.../linux/linux-yocto-rt_6.6.bb | 6 ++--
.../linux/linux-yocto-tiny_6.1.bb | 6 ++--
.../linux/linux-yocto-tiny_6.6.bb | 6 ++--
meta/recipes-kernel/linux/linux-yocto_6.1.bb | 28 +++++++--------
meta/recipes-kernel/linux/linux-yocto_6.6.bb | 28 +++++++--------
8 files changed, 92 insertions(+), 52 deletions(-)
--
2.39.2
next reply other threads:[~2024-01-19 21:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-19 21:14 bruce.ashfield [this message]
2024-01-19 21:14 ` [PATCH 01/11] linux-yocto/6.6: update to v6.6.11 bruce.ashfield
2024-01-19 21:14 ` [PATCH 02/11] linux-yocto/6.6: update CVE exclusions bruce.ashfield
2024-01-19 21:14 ` [PATCH 03/11] linux-yocto/6.1: update to v6.1.72 bruce.ashfield
2024-01-19 21:14 ` [PATCH 04/11] linux-yocto/6.1: update CVE exclusions bruce.ashfield
2024-01-19 21:14 ` [PATCH 05/11] linux-yocto/6.6: cfg: arm: introduce page size fragments bruce.ashfield
2024-01-19 21:14 ` [PATCH 06/11] linux-yocto/6.6: security/cfg: add configs to harden protection bruce.ashfield
2024-01-19 21:14 ` [PATCH 07/11] linux-yocto/6.1: " bruce.ashfield
2024-01-19 21:14 ` [PATCH 08/11] linux-yocto/6.6: update to v6.6.12 bruce.ashfield
2024-01-19 21:14 ` [PATCH 09/11] linux-yocto/6.6: update CVE exclusions bruce.ashfield
2024-01-19 21:14 ` [PATCH 10/11] linux-yocto/6.1: update to v6.1.73 bruce.ashfield
2024-01-19 21:14 ` [PATCH 11/11] linux-yocto/6.1: update CVE exclusions bruce.ashfield
2024-01-26 16:45 ` [OE-core] [PATCH 00/11] linux-yocto: consolidated pull request Alexandre Belloni
2024-01-26 18:16 ` Bruce Ashfield
-- strict thread matches above, loose matches on Subject: below --
2020-11-17 15:24 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.1705698717.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