From: Anuj Mittal <anuj.mittal@intel.com>
To: openembedded-core@lists.openembedded.org,
richard.purdie@linuxfoundation.org
Subject: [honister][PATCH 00/11] Pull request
Date: Tue, 4 Jan 2022 14:21:05 +0800 [thread overview]
Message-ID: <cover.1641277164.git.anuj.mittal@intel.com> (raw)
Please merge these changes.
Thanks,
Anuj
The following changes since commit 067fbe5e12a81225cf3ff436837af6a6d23040a6:
license.bbclass: implement ast.NodeVisitor.visit_Constant (2021-12-13 12:19:03 +0800)
are available in the Git repository at:
git://push.openembedded.org/openembedded-core-contrib anujm/honister
Anuj Mittal (1):
xserver-xorg: upgrade 1.20.13 -> 1.20.14
Bruce Ashfield (3):
linux-yocto/5.10: update to v5.10.84
linux-yocto/5.10: update to v5.10.85
linux-yocto/5.10: update to v5.10.87
Chaitanya Vadrevu (1):
python3-pyelftools: Depend on debugger, pprint
Florian Amstutz (1):
systemd: Fix systemd-journal-gateway user/groups
Pgowda (1):
gcc: Fix CVE-2021-35465
Richard Purdie (1):
oeqa/selftest/bbtests: Use YP sources mirror instead of GNU
pgowda (2):
gcc: Fix CVE-2021-42574
binutils: CVE-2021-42574
wangmy (1):
linux-firmware: upgrade 20211027 -> 20211216
meta/lib/oeqa/selftest/cases/bbtests.py | 2 +-
meta/recipes-core/systemd/systemd_249.7.bb | 4 +-
.../binutils/binutils-2.37.inc | 1 +
.../binutils/0001-CVE-2021-42574.patch | 2001 +++++++++++++++
meta/recipes-devtools/gcc/gcc-11.2.inc | 8 +
.../gcc/gcc/0001-CVE-2021-35465.patch | 138 +
.../gcc/gcc/0001-CVE-2021-42574.patch | 2282 +++++++++++++++++
.../gcc/gcc/0002-CVE-2021-35465.patch | 39 +
.../gcc/gcc/0002-CVE-2021-42574.patch | 1765 +++++++++++++
.../gcc/gcc/0003-CVE-2021-35465.patch | 103 +
.../gcc/gcc/0003-CVE-2021-42574.patch | 142 +
.../gcc/gcc/0004-CVE-2021-35465.patch | 304 +++
.../gcc/gcc/0004-CVE-2021-42574.patch | 573 +++++
.../python/python3-pyelftools_0.27.bb | 2 +
...org_1.20.13.bb => xserver-xorg_1.20.14.bb} | 2 +-
...20211027.bb => linux-firmware_20211216.bb} | 4 +-
.../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 +-
19 files changed, 7383 insertions(+), 25 deletions(-)
create mode 100644 meta/recipes-devtools/binutils/binutils/0001-CVE-2021-42574.patch
create mode 100644 meta/recipes-devtools/gcc/gcc/0001-CVE-2021-35465.patch
create mode 100644 meta/recipes-devtools/gcc/gcc/0001-CVE-2021-42574.patch
create mode 100644 meta/recipes-devtools/gcc/gcc/0002-CVE-2021-35465.patch
create mode 100644 meta/recipes-devtools/gcc/gcc/0002-CVE-2021-42574.patch
create mode 100644 meta/recipes-devtools/gcc/gcc/0003-CVE-2021-35465.patch
create mode 100644 meta/recipes-devtools/gcc/gcc/0003-CVE-2021-42574.patch
create mode 100644 meta/recipes-devtools/gcc/gcc/0004-CVE-2021-35465.patch
create mode 100644 meta/recipes-devtools/gcc/gcc/0004-CVE-2021-42574.patch
rename meta/recipes-graphics/xorg-xserver/{xserver-xorg_1.20.13.bb => xserver-xorg_1.20.14.bb} (93%)
rename meta/recipes-kernel/linux-firmware/{linux-firmware_20211027.bb => linux-firmware_20211216.bb} (99%)
--
2.33.1
reply other threads:[~2022-01-04 6:21 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.1641277164.git.anuj.mittal@intel.com \
--to=anuj.mittal@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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