From: Steve Sakoman <steve@sakoman.com>
To: openembedded-core@lists.openembedded.org
Subject: [OE-core][kirkstone 00/13] Pull request (cover letter only)
Date: Sat, 4 Feb 2023 04:32:56 -1000 [thread overview]
Message-ID: <cover.1675521082.git.steve@sakoman.com> (raw)
The following changes since commit a8c82902384f7430519a31732a4bb631f21693ac:
build-appliance-image: Update to kirkstone head revision (2023-01-26 23:40:27 +0000)
are available in the Git repository at:
https://git.openembedded.org/openembedded-core-contrib stable/kirkstone-next
http://cgit.openembedded.org/openembedded-core-contrib/log/?h=stable/kirkstone-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
Khem Raj (3):
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'
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: set correct branch name
quilt: use upstreamed faildiff.test fix
Thomas Roos (1):
devtool: fix devtool finish when gitmodules file is empty
Xiangyu Chen (1):
numactl: skip test case when target platform doesn't have 2 CPU node
meta/classes/core-image.bbclass | 2 +-
meta/classes/externalsrc.bbclass | 2 +-
meta/classes/native.bbclass | 2 +-
meta/classes/populate_sdk_ext.bbclass | 2 +-
.../distro/include/ptest-packagelists.inc | 2 +-
.../ppp/ppp/CVE-2022-4603.patch | 48 +++++++++++++++
meta/recipes-connectivity/ppp/ppp_2.4.9.bb | 1 +
meta/recipes-devtools/quilt/quilt.inc | 1 +
.../quilt/quilt/faildiff-order.patch | 41 +++++++++++++
.../libtirpc/libtirpc_1.3.2.bb | 2 +-
.../spir/spirv-headers_1.3.204.1.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 +++++++++++++++++++
.../lttng/lttng-modules_2.13.8.bb | 2 +
...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 +-
21 files changed, 292 insertions(+), 34 deletions(-)
create mode 100644 meta/recipes-connectivity/ppp/ppp/CVE-2022-4603.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
create mode 100644 meta/recipes-support/libusb/libusb1/0001-configure.ac-Link-with-latomic-only-if-no-atomic-bui.patch
--
2.25.1
next reply other threads:[~2023-02-04 14:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-04 14:32 Steve Sakoman [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-10-20 14:25 [OE-core][kirkstone 00/13] Pull request (cover letter only) Steve Sakoman
2022-06-23 22:48 Steve Sakoman
2022-06-08 21:50 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.1675521082.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