From: "Anuj Mittal" <anuj.mittal@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [hardknott][PATCH 00/13] pull request (cover letter only)
Date: Thu, 24 Jun 2021 14:30:10 +0800 [thread overview]
Message-ID: <cover.1624516137.git.anuj.mittal@intel.com> (raw)
Please merge these changes in hardknott.
Thanks,
Anuj
The following changes since commit bfe25c99e914062b0527a6e74ebb8ce1eaad4ca8:
linux-firmware: upgrade 20210315 -> 20210511 (2021-06-11 11:46:53 +0800)
are available in the Git repository at:
git://push.openembedded.org/openembedded-core-contrib stable/hardknott-next
Andrea Adami (1):
kernel.bbclass: fix do_sizecheck() comparison
Bruce Ashfield (2):
linux-yocto/5.4: update to v5.4.124
linux-yocto/5.4: update to v5.4.125
Kai Kang (1):
libx11: fix CVE-2021-31535
Khem Raj (1):
linuxloader: Be aware of riscv32 ldso
Peter Kjellerstedt (2):
util-linux.inc: Do not modify BPN
native.bbclass: Do not remove "-native" in the middle of recipe names
Richard Purdie (2):
lttng-tools: upgrade 2.12.3 -> 2.12.4
perf: Use python3targetconfig to ensure we use target libraries
Ross Burton (1):
avahi: apply fix for CVE-2021-3468
Tony Tascioglu (2):
valgrind: remove buggy ptest from arm64
valgrind: Actually install list of non-deterministic ptests
Trevor Gamblin (1):
curl: cleanup CVE patches for hardknott
meta/classes/kernel.bbclass | 2 +-
meta/classes/linuxloader.bbclass | 2 +
meta/classes/native.bbclass | 8 +-
meta/recipes-connectivity/avahi/avahi_0.8.bb | 1 +
.../avahi/files/handle-hup.patch | 41 +++
meta/recipes-core/util-linux/util-linux.inc | 3 +-
.../valgrind/valgrind/remove-for-aarch64 | 1 +
.../valgrind/valgrind/run-ptest | 4 +-
.../valgrind/taskset_nondeterministic_tests | 2 -
.../valgrind/valgrind_3.16.1.bb | 2 +
.../xorg-lib/libx11/fix-CVE-2021-31535.patch | 320 ++++++++++++++++++
.../recipes-graphics/xorg-lib/libx11_1.7.0.bb | 5 +-
.../linux/linux-yocto-rt_5.4.bb | 6 +-
.../linux/linux-yocto-tiny_5.4.bb | 8 +-
meta/recipes-kernel/linux/linux-yocto_5.4.bb | 22 +-
...-tools_2.12.3.bb => lttng-tools_2.12.4.bb} | 9 +-
meta/recipes-kernel/perf/perf.bb | 2 +-
...-argument-to-Curl_ssl_get-addsession.patch | 16 +-
...redentials-from-the-auto-referer-hea.patch | 5 +-
19 files changed, 417 insertions(+), 42 deletions(-)
create mode 100644 meta/recipes-connectivity/avahi/files/handle-hup.patch
create mode 100644 meta/recipes-graphics/xorg-lib/libx11/fix-CVE-2021-31535.patch
rename meta/recipes-kernel/lttng/{lttng-tools_2.12.3.bb => lttng-tools_2.12.4.bb} (94%)
--
2.31.1
reply other threads:[~2021-06-24 6:30 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.1624516137.git.anuj.mittal@intel.com \
--to=anuj.mittal@intel.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.