From: "Anuj Mittal" <anuj.mittal@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [hardknott][PATCH 00/11] Pull request (cover letter only)
Date: Thu, 9 Sep 2021 09:19:18 +0800 [thread overview]
Message-ID: <cover.1631150280.git.anuj.mittal@intel.com> (raw)
Please merge these changes.
Thanks,
Anuj
The following changes since commit e3a7eaf9fe1420b2525e14f0c0f2936e7818b8a3:
build-appliance-image: Update to hardknott head revision (2021-09-01 16:28:21 +0100)
are available in the Git repository at:
git://push.openembedded.org/openembedded-core-contrib stable/hardknott-next
Andrej Valek (1):
vim: add option to disable NLS support
Armin Kuster (1):
lz4: Security Fix for CVE-2021-3520
Bruce Ashfield (3):
linux-yocto/5.10: update to v5.10.59
linux-yocto/5.10: update to v5.10.60
parselogs.py: ignore intermittent CD/DVDROM identification failure
Paul Barker (1):
kernel-yocto: Simplify no git repo case in do_kernel_checkout
Richard Purdie (3):
sdk: Decouple default install path from built in path
oeqa/runtime/parselogs: Make DVD ata error apply to all qemux86
machines
xdg-utils: Add fix for CVE-2020-27748
Ross Burton (1):
cpio: backport fix for CVE-2021-38185
Trevor Gamblin (1):
bluez5: fix CVE-2021-3658
meta/classes/kernel-yocto.bbclass | 30 +-
meta/classes/populate_sdk_base.bbclass | 1 +
meta/conf/bitbake.conf | 4 +-
meta/files/toolchain-shar-extract.sh | 3 +-
meta/files/toolchain-shar-relocate.sh | 2 +-
meta/lib/oeqa/runtime/cases/parselogs.py | 1 +
meta/recipes-connectivity/bluez5/bluez5.inc | 1 +
...ter-Fix-storing-discoverable-setting.patch | 100 +++
.../cpio/cpio-2.13/CVE-2021-38185.patch | 581 ++++++++++++++++++
meta/recipes-extended/cpio/cpio_2.13.bb | 1 +
...9813e0eb0246f63b54e9e154970e609575af.patch | 58 ++
.../xdg-utils/xdg-utils_1.1.3.bb | 1 +
.../linux/linux-yocto-rt_5.10.bb | 6 +-
.../linux/linux-yocto-tiny_5.10.bb | 8 +-
meta/recipes-kernel/linux/linux-yocto_5.10.bb | 24 +-
.../lz4/files/CVE-2021-3520.patch | 27 +
meta/recipes-support/lz4/lz4_1.9.3.bb | 1 +
meta/recipes-support/vim/vim.inc | 4 +-
18 files changed, 815 insertions(+), 38 deletions(-)
create mode 100644 meta/recipes-connectivity/bluez5/bluez5/0001-adapter-Fix-storing-discoverable-setting.patch
create mode 100644 meta/recipes-extended/cpio/cpio-2.13/CVE-2021-38185.patch
create mode 100644 meta/recipes-extended/xdg-utils/xdg-utils/1f199813e0eb0246f63b54e9e154970e609575af.patch
create mode 100644 meta/recipes-support/lz4/files/CVE-2021-3520.patch
--
2.31.1
next reply other threads:[~2021-09-09 1:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-09 1:19 Anuj Mittal [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-10-06 15:13 [hardknott][PATCH 00/11] Pull request (cover letter only) Anuj Mittal
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.1631150280.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.