From: Steve Sakoman <steve@sakoman.com>
To: openembedded-core@lists.openembedded.org
Subject: [OE-core][langdale 00/22] Pull request (cover letter only)
Date: Wed, 7 Dec 2022 04:42:07 -1000 [thread overview]
Message-ID: <cover.1670424077.git.steve@sakoman.com> (raw)
The following changes since commit 30cdb7fbec8e9cf5c5a25e28a1102fa562a7f6c2:
create-spdx: default share_src for shared sources (2022-11-25 06:16:14 -1000)
are available in the Git repository at:
https://git.openembedded.org/openembedded-core-contrib stable/langdale-next
http://cgit.openembedded.org/openembedded-core-contrib/log/?h=stable/langdale-next
Bruce Ashfield (11):
linux-yocto/5.15: update to v5.15.74
linux-yocto/5.15: update to v5.15.76
linux-yocto/5.15: update to v5.15.78
linux-yocto/5.15: fix CONFIG_CRYPTO_CCM mismatch warnings
linux-yocto/5.19: update to v5.19.16
linux-yocto/5.19: update to v5.19.17
linux-yocto/5.19: cfg: intel and vesa updates
linux-yocto/5.19: security.cfg: remove configs which have been dropped
linux-yocto/5.19: fix CONFIG_CRYPTO_CCM mismatch warnings
linux-yocto/5.19: fix elfutils run-backtrace-native-core ptest failure
kern-tools: integrate ZFS speedup patch
Chen Qi (3):
kernel.bbclass: make KERNEL_DEBUG_TIMESTAMPS work at rebuild
dhcpcd: fix to work with systemd
resolvconf: make it work
Dmitry Baryshkov (2):
linux-firmware: upgrade 20221012 -> 20221109
linux-firmware: add new fw file to ${PN}-qcom-adreno-a530
Enrico Jörns (1):
sstatesig: emit more helpful error message when not finding sstate
manifest
Narpat Mali (2):
ffmpeg: fix for CVE-2022-3964
ffmpeg: fix for CVE-2022-3965
Polampalli, Archana (1):
libpam: fix CVE-2022-28321
Qiu, Zheng (1):
tiff: Security fix for CVE-2022-3970
Tim Orling (1):
mirrors.bbclass: update CPAN_MIRROR
meta/classes-global/mirrors.bbclass | 3 +-
meta/classes-recipe/kernel.bbclass | 8 +
meta/lib/oe/sstatesig.py | 6 +-
.../dhcpcd/dhcpcd_9.4.1.bb | 1 +
...mprove-the-sitation-of-working-with-.patch | 82 +++++++
...01-avoid-using-m-option-for-readlink.patch | 37 ++++
.../resolvconf/resolvconf_1.91.bb | 9 +-
.../pam/libpam/CVE-2022-28321-0002.patch | 205 ++++++++++++++++++
meta/recipes-extended/pam/libpam_1.5.2.bb | 1 +
.../kern-tools/kern-tools-native_git.bb | 2 +-
...20221012.bb => linux-firmware_20221109.bb} | 6 +-
.../linux/linux-yocto-rt_5.15.bb | 6 +-
.../linux/linux-yocto-rt_5.19.bb | 6 +-
.../linux/linux-yocto-tiny_5.15.bb | 6 +-
.../linux/linux-yocto-tiny_5.19.bb | 6 +-
meta/recipes-kernel/linux/linux-yocto_5.15.bb | 26 +--
meta/recipes-kernel/linux/linux-yocto_5.19.bb | 26 +--
...c-stop-accessing-out-of-bounds-frame.patch | 89 ++++++++
...c-stop-accessing-out-of-bounds-frame.patch | 108 +++++++++
.../recipes-multimedia/ffmpeg/ffmpeg_5.1.2.bb | 6 +-
.../libtiff/files/CVE-2022-3970.patch | 39 ++++
meta/recipes-multimedia/libtiff/tiff_4.4.0.bb | 1 +
22 files changed, 629 insertions(+), 50 deletions(-)
create mode 100644 meta/recipes-connectivity/dhcpcd/files/0001-20-resolv.conf-improve-the-sitation-of-working-with-.patch
create mode 100644 meta/recipes-connectivity/resolvconf/resolvconf/0001-avoid-using-m-option-for-readlink.patch
create mode 100644 meta/recipes-extended/pam/libpam/CVE-2022-28321-0002.patch
rename meta/recipes-kernel/linux-firmware/{linux-firmware_20221012.bb => linux-firmware_20221109.bb} (99%)
create mode 100644 meta/recipes-multimedia/ffmpeg/ffmpeg/0001-avcodec-rpzaenc-stop-accessing-out-of-bounds-frame.patch
create mode 100644 meta/recipes-multimedia/ffmpeg/ffmpeg/0001-avcodec-smcenc-stop-accessing-out-of-bounds-frame.patch
create mode 100644 meta/recipes-multimedia/libtiff/files/CVE-2022-3970.patch
--
2.25.1
next reply other threads:[~2022-12-07 14:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 14:42 Steve Sakoman [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-01-04 14:38 [OE-core][langdale 00/22] Pull request (cover letter only) Steve Sakoman
2023-01-06 14:33 ` Steve Sakoman
2023-01-06 17:43 ` Richard Purdie
2023-02-23 14:16 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.1670424077.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.