From: Anuj Mittal <anuj.mittal@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [honister][PATCH 0/5] Review request
Date: Mon, 22 Nov 2021 16:34:01 +0800 [thread overview]
Message-ID: <cover.1637569916.git.anuj.mittal@intel.com> (raw)
Please review these changes. No issues seen while testing on
autobuilder.
https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/2940
Thanks,
Anuj
The following changes since commit 9f3fbfc02ae6fadffbcc1bda1fa75dfe140d05c5:
insane.bbclass: Add a check for directories that are expected to be empty (2021-11-16 13:09:56 +0800)
are available in the Git repository at:
git://push.openembedded.org/openembedded-core-contrib anujm/honister
Andres Beltran (1):
create-spdx: Fix key errors in do_create_runtime_spdx
Claus Stovgaard (1):
cups: Fix missing installation of cups sysv init scripts
Richard Purdie (1):
glibc: Backport fix for CVE-2021-43396
Saul Wold (2):
create_spdx: ensure is_work_shared() is unique
create-spdx: Protect against None from LICENSE_PATH
meta/classes/create-spdx.bbclass | 18 +-
.../glibc/glibc/CVE-2021-43396.patch | 184 ++++++++++++++++++
meta/recipes-core/glibc/glibc_2.34.bb | 1 +
meta/recipes-extended/cups/cups.inc | 2 +-
4 files changed, 195 insertions(+), 10 deletions(-)
create mode 100644 meta/recipes-core/glibc/glibc/CVE-2021-43396.patch
--
2.33.1
next reply other threads:[~2021-11-22 8:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-22 8:34 Anuj Mittal [this message]
2021-11-22 8:34 ` [honister][PATCH 1/5] cups: Fix missing installation of cups sysv init scripts Anuj Mittal
2021-11-22 8:34 ` [honister][PATCH 2/5] glibc: Backport fix for CVE-2021-43396 Anuj Mittal
2021-11-22 8:34 ` [honister][PATCH 3/5] create_spdx: ensure is_work_shared() is unique Anuj Mittal
2021-11-22 8:34 ` [honister][PATCH 4/5] create-spdx: Protect against None from LICENSE_PATH Anuj Mittal
2021-11-22 8:34 ` [honister][PATCH 5/5] create-spdx: Fix key errors in do_create_runtime_spdx 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.1637569916.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox