From: Steve Sakoman <steve@sakoman.com>
To: openembedded-core@lists.openembedded.org
Subject: [OE-core][langdale 00/17] Pull request (cover letter only)
Date: Sat, 4 Feb 2023 04:29:15 -1000 [thread overview]
Message-ID: <cover.1675520886.git.steve@sakoman.com> (raw)
The following changes since commit cfd9f549a0d5dd44f4c71bd077b5fd17d3683550:
selftest/virgl: use pkg-config from the host (2023-01-19 16:28:32 -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
Armin Kuster (1):
lttng-modules: Fix for 5.10.163 kernel version
Bruce Ashfield (1):
linux-yocto/5.15: update to v5.15.87
He Zhe (1):
lttng-modules: update 2.13.7 -> 2.13.8
Khem Raj (4):
createrepo-c: Include missing rpm/rpmstring.h
libtirpc: Check if file exists before operating on it
libusb1: Link with latomic only if compiler has no atomic builtins
libusb1: Strip trailing whitespaces
Niko Mauno (1):
Fix missing leading whitespace with ':append'
Peter Kjellerstedt (1):
librsvg: Only enable the Vala bindings if GObject Introspection is
enabled
Richard Purdie (1):
native: Drop special variable handling
Ross Burton (4):
ppp: backport fix for CVE-2022-4603
quilt: fix intermittent failure in faildiff.test
spirv-headers/spirv-tools: set correct branch name
quilt: use upstreamed faildiff.test fix
Thomas Roos (1):
devtool: fix devtool finish when gitmodules file is empty
Vivek Kumbhar (1):
openssl: fix CVE-2022-3996 double locking leads to denial of service
Xiangyu Chen (1):
numactl: skip test case when target platform doesn't have 2 CPU node
meta/classes-recipe/core-image.bbclass | 2 +-
meta/classes-recipe/native.bbclass | 2 +-
meta/classes-recipe/populate_sdk_ext.bbclass | 2 +-
meta/classes/externalsrc.bbclass | 2 +-
.../distro/include/ptest-packagelists.inc | 2 +-
.../openssl/openssl/CVE-2022-3996.patch | 43 +++++++++++++
.../openssl/openssl_3.0.7.bb | 1 +
.../ppp/ppp/CVE-2022-4603.patch | 48 +++++++++++++++
meta/recipes-connectivity/ppp/ppp_2.4.9.bb | 1 +
.../0001-include-rpm-rpmstring.h.patch | 27 ++++++++
.../createrepo-c/createrepo-c_0.20.1.bb | 1 +
meta/recipes-devtools/quilt/quilt.inc | 1 +
.../quilt/quilt/faildiff-order.patch | 41 +++++++++++++
.../libtirpc/libtirpc_1.3.3.bb | 2 +-
meta/recipes-gnome/librsvg/librsvg_2.54.5.bb | 4 +-
.../spir/spirv-headers_1.3.216.0.bb | 2 +-
.../spir/spirv-tools_1.3.216.0.bb | 2 +-
.../linux/linux-yocto-rt_5.15.bb | 6 +-
.../linux/linux-yocto-tiny_5.15.bb | 6 +-
meta/recipes-kernel/linux/linux-yocto_5.15.bb | 26 ++++----
.../fix-jbd2-upper-bound-for-v5.10.163.patch | 52 ++++++++++++++++
...e-the-correct-print-format-v5.10.163.patch | 61 +++++++++++++++++++
...ules_2.13.7.bb => lttng-modules_2.13.8.bb} | 4 +-
...k-with-latomic-only-if-no-atomic-bui.patch | 46 ++++++++++++++
meta/recipes-support/libusb/libusb1_1.0.26.bb | 13 ++--
.../numactl/Fix-the-test-output-format.patch | 3 +-
.../recipes-support/numactl/numactl/run-ptest | 6 +-
27 files changed, 368 insertions(+), 38 deletions(-)
create mode 100644 meta/recipes-connectivity/openssl/openssl/CVE-2022-3996.patch
create mode 100644 meta/recipes-connectivity/ppp/ppp/CVE-2022-4603.patch
create mode 100644 meta/recipes-devtools/createrepo-c/createrepo-c/0001-include-rpm-rpmstring.h.patch
create mode 100644 meta/recipes-devtools/quilt/quilt/faildiff-order.patch
create mode 100644 meta/recipes-kernel/lttng/lttng-modules/fix-jbd2-upper-bound-for-v5.10.163.patch
create mode 100644 meta/recipes-kernel/lttng/lttng-modules/fix-jbd2-use-the-correct-print-format-v5.10.163.patch
rename meta/recipes-kernel/lttng/{lttng-modules_2.13.7.bb => lttng-modules_2.13.8.bb} (87%)
create mode 100644 meta/recipes-support/libusb/libusb1/0001-configure.ac-Link-with-latomic-only-if-no-atomic-bui.patch
--
2.25.1
reply other threads:[~2023-02-04 14:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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.1675520886.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.