From: Steve Sakoman <steve@sakoman.com>
To: openembedded-core@lists.openembedded.org
Subject: [OE-core][kirkstone 0/3] Patch review
Date: Tue, 16 Sep 2025 07:17:45 -0700 [thread overview]
Message-ID: <cover.1758032126.git.steve@sakoman.com> (raw)
Please review this set of changes for kirkstone and have comments back by
end of day Thursday, September 18
Passed a-full on autobuilder:
https://autobuilder.yoctoproject.org/valkyrie/#/builders/29/builds/2381
The following changes since commit 3dd917c52ace30607800f0b70a52a52662dda731:
wpa-supplicant: fix CVE-2022-37660 (2025-09-09 09:01:30 -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
Hitendra Prajapati (1):
go: ignore CVE-2024-24790
Philip Lorenz (1):
insane: Ensure that `src-uri-bad` fails correctly
Richard Purdie (1):
insane: Improve patch warning/error handling
meta/classes/insane.bbclass | 24 ++++++++++++++++--------
meta/recipes-devtools/go/go-1.17.13.inc | 3 ++-
2 files changed, 18 insertions(+), 9 deletions(-)
--
2.43.0
next reply other threads:[~2025-09-16 14:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-16 14:17 Steve Sakoman [this message]
2025-09-16 14:17 ` [OE-core][kirkstone 1/3] go: ignore CVE-2024-24790 Steve Sakoman
2025-09-16 14:17 ` [OE-core][kirkstone 2/3] insane: Improve patch warning/error handling Steve Sakoman
2025-09-16 14:17 ` [OE-core][kirkstone 3/3] insane: Ensure that `src-uri-bad` fails correctly Steve Sakoman
-- strict thread matches above, loose matches on Subject: below --
2025-02-13 14:26 [OE-core][kirkstone 0/3] Patch review Steve Sakoman
2023-10-31 22:05 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.1758032126.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.