From: Steve Sakoman <steve@sakoman.com>
To: openembedded-core@lists.openembedded.org
Subject: [OE-core][kirkstone 0/5] Patch review
Date: Wed, 6 Nov 2024 05:33:17 -0800 [thread overview]
Message-ID: <cover.1730899830.git.steve@sakoman.com> (raw)
Please review this set of changes for kirkstone and have comments back by
end of day Friday, November 8
Passed a-full on autobuilder:
https://valkyrie.yoctoproject.org/#/builders/29/builds/398
The following changes since commit 2c913a7b66ea756ebc65a573e1b5bb5dba6834d2:
util-linux: Define pidfd_* function signatures (2024-10-29 07:51:17 -0700)
are available in the Git repository at:
https://git.openembedded.org/openembedded-core-contrib stable/kirkstone-nut
https://git.openembedded.org/openembedded-core-contrib/log/?h=stable/kirkstone-nut
Martin Jansa (1):
xmlto: backport a patch to fix build with gcc-14 on host
Peter Marko (1):
zstd: patch CVE-2022-4899
Richard Purdie (2):
cve_check: Use a local copy of the database during builds
package: Switch debug source handling to use prefix map
Ruiqiang Hao (1):
gcc: restore a patch for Neoverse N2 core
meta/classes/cve-check.bbclass | 7 +-
meta/classes/package.bbclass | 68 +-
.../meta/cve-update-nvd2-native.bb | 18 +-
meta/recipes-devtools/gcc/gcc-11.5.inc | 1 +
...4-Update-Neoverse-N2-core-definition.patch | 40 +
...001-Fix-return-type-of-main-function.patch | 42 +
...mlif.c-and-update-xmlif.l-to-comply-.patch | 1259 +++++++++++++++++
.../0001-fix-Wimplicit-int-for-ifsense.patch | 33 +
meta/recipes-devtools/xmlto/xmlto_0.0.28.bb | 10 +
.../zstd/zstd/CVE-2022-4899-1.patch | 66 +
.../zstd/zstd/CVE-2022-4899-2.patch | 83 ++
meta/recipes-extended/zstd/zstd_1.5.2.bb | 5 +-
12 files changed, 1583 insertions(+), 49 deletions(-)
create mode 100644 meta/recipes-devtools/gcc/gcc/0001-aarch64-Update-Neoverse-N2-core-definition.patch
create mode 100644 meta/recipes-devtools/xmlto/xmlto-0.0.28/0001-Fix-return-type-of-main-function.patch
create mode 100644 meta/recipes-devtools/xmlto/xmlto-0.0.28/0001-Regenerate-the-xmlif.c-and-update-xmlif.l-to-comply-.patch
create mode 100644 meta/recipes-devtools/xmlto/xmlto-0.0.28/0001-fix-Wimplicit-int-for-ifsense.patch
create mode 100644 meta/recipes-extended/zstd/zstd/CVE-2022-4899-1.patch
create mode 100644 meta/recipes-extended/zstd/zstd/CVE-2022-4899-2.patch
--
2.34.1
next reply other threads:[~2024-11-06 13:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-06 13:33 Steve Sakoman [this message]
2024-11-06 13:33 ` [OE-core][kirkstone 1/5] zstd: patch CVE-2022-4899 Steve Sakoman
2024-11-06 13:33 ` [OE-core][kirkstone 2/5] cve_check: Use a local copy of the database during builds Steve Sakoman
2024-11-06 13:33 ` [OE-core][kirkstone 3/5] gcc: restore a patch for Neoverse N2 core Steve Sakoman
2024-11-06 13:33 ` [OE-core][kirkstone 4/5] package: Switch debug source handling to use prefix map Steve Sakoman
2024-11-06 13:33 ` [OE-core][kirkstone 5/5] xmlto: backport a patch to fix build with gcc-14 on host Steve Sakoman
-- strict thread matches above, loose matches on Subject: below --
2025-09-09 19:29 [OE-core][kirkstone 0/5] Patch review Steve Sakoman
2024-10-17 13:31 Steve Sakoman
2024-10-09 16:16 Steve Sakoman
2024-07-31 12:02 Steve Sakoman
2024-04-29 12:53 Steve Sakoman
2023-12-12 22:40 Steve Sakoman
2022-09-14 19:10 Steve Sakoman
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.1730899830.git.steve@sakoman.com \
--to=steve@sakoman.com \
--cc=openembedded-core@lists.openembedded.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.