From: Steve Sakoman <steve@sakoman.com>
To: openembedded-core@lists.openembedded.org
Subject: [OE-core][walnascar 0/7] Patch review
Date: Sat, 21 Jun 2025 07:23:10 -0700 [thread overview]
Message-ID: <cover.1750515680.git.steve@sakoman.com> (raw)
Please review this set of changes for walnascar and have comments back by
end of day Tuesday, June 24
Passed a-full on autobuilder:
https://autobuilder.yoctoproject.org/valkyrie/#/builders/29/builds/1854
The following changes since commit fd79c20430ad5c540522ddbe72ef235379c628bd:
tune-cortexr52: Remove aarch64 for ARM Cortex-R52 (2025-06-16 12:50:00 -0700)
are available in the Git repository at:
https://git.openembedded.org/openembedded-core-contrib stable/walnascar-nut
https://git.openembedded.org/openembedded-core-contrib/log/?h=stable/walnascar-nut
Archana Polampalli (1):
ghostscript: upgrade 10.05.0 -> 10.05.1
Moritz Haase (1):
cmake: Correctly handle cost data of tests with arbitrary chars in
name
Peter Marko (2):
go: set status of CVE-2024-3566
glibc: stable 2.41 branch updates
Praveen Kumar (1):
bind: upgrade 9.20.8 -> 9.20.9
Richard Purdie (1):
bind: upgrade 9.20.6 -> 9.20.7
Wang Mingyu (1):
bind: upgrade 9.20.7 -> 9.20.8
...1-avoid-start-failure-with-bind-user.patch | 2 +-
...d-V-and-start-log-hide-build-options.patch | 4 +-
...ching-for-json-headers-searches-sysr.patch | 4 +-
.../recipes-connectivity/bind/bind/conf.patch | 2 +-
...t.d-add-support-for-read-only-rootfs.patch | 2 +-
.../bind/make-etc-initd-bind-stop-work.patch | 2 +-
.../bind/{bind_9.20.6.bb => bind_9.20.9.bb} | 2 +-
meta/recipes-core/glibc/glibc-version.inc | 2 +-
...u-tests-that-can-hang-in-oe-selftest.patch | 2 +-
meta/recipes-core/glibc/glibc_2.41.bb | 2 +-
.../cmake/cmake-native_3.31.6.bb | 2 +-
...trary-characters-in-test-names-of-CT.patch | 202 ++++++++++++++++++
meta/recipes-devtools/cmake/cmake_3.31.6.bb | 1 +
.../go/go-binary-native_1.24.4.bb | 1 +
meta/recipes-devtools/go/go-common.inc | 1 +
...ript_10.05.0.bb => ghostscript_10.05.1.bb} | 2 +-
16 files changed, 219 insertions(+), 14 deletions(-)
rename meta/recipes-connectivity/bind/{bind_9.20.6.bb => bind_9.20.9.bb} (97%)
create mode 100644 meta/recipes-devtools/cmake/cmake/0001-ctest-Allow-arbitrary-characters-in-test-names-of-CT.patch
rename meta/recipes-extended/ghostscript/{ghostscript_10.05.0.bb => ghostscript_10.05.1.bb} (97%)
--
2.43.0
next reply other threads:[~2025-06-21 14:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-21 14:23 Steve Sakoman [this message]
2025-06-21 14:23 ` [OE-core][walnascar 1/7] go: set status of CVE-2024-3566 Steve Sakoman
2025-06-21 14:23 ` [OE-core][walnascar 2/7] glibc: stable 2.41 branch updates Steve Sakoman
2025-06-21 14:23 ` [OE-core][walnascar 3/7] bind: upgrade 9.20.6 -> 9.20.7 Steve Sakoman
2025-06-21 14:23 ` [OE-core][walnascar 4/7] bind: upgrade 9.20.7 -> 9.20.8 Steve Sakoman
2025-06-21 14:23 ` [OE-core][walnascar 5/7] bind: upgrade 9.20.8 -> 9.20.9 Steve Sakoman
2025-06-21 14:23 ` [OE-core][walnascar 6/7] ghostscript: upgrade 10.05.0 -> 10.05.1 Steve Sakoman
2025-06-21 14:23 ` [OE-core][walnascar 7/7] cmake: Correctly handle cost data of tests with arbitrary chars in name Steve Sakoman
-- strict thread matches above, loose matches on Subject: below --
2025-09-23 14:38 [OE-core][walnascar 0/7] Patch review 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.1750515680.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox