From: Anuj Mittal <anuj.mittal@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [hardknott][PATCH 00/15] Patch review
Date: Tue, 8 Mar 2022 22:19:51 +0800 [thread overview]
Message-ID: <cover.1646748869.git.anuj.mittal@intel.com> (raw)
Next set of changes for hardknott. Please review.
No problems seen while testing on autobuilder.
https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/3338
Thanks,
Anuj
The following changes since commit 94db7109f21cdefd50baea5660b691e5fe44a0d1:
scripts/buildhistory-diff: drop use of distutils (2022-02-25 22:14:02 +0800)
are available in the Git repository at:
git://push.openembedded.org/openembedded-core-contrib anujm/hardknott
Anuj Mittal (1):
lttng-modules: upgrade 2.12.6 -> 2.12.7
Bruce Ashfield (6):
linux-yocto/5.10: ppc/riscv: fix build with binutils 2.3.8
linux-yocto/5.10: fix dssall build error with binutils 2.3.8
linux-yocto/5.10: features/zram: remove CONFIG_ZRAM_DEF_COMP
linux-yocto/5.10: update to v5.10.101
linux-yocto/5.10: Fix ramoops/ftrace
linux-yocto/5.10: update to v5.10.103
Changqing Li (1):
unfs3: correct configure option
Lee Chee Yang (1):
ruby : update to 3.0.3
Minjae Kim (1):
ghostscript: fix CVE-2021-45949
Peter Kjellerstedt (1):
selftest: recipetool: Correct the URI for socat
Richard Purdie (1):
libgcrypt: Upgrade 1.9.3 -> 1.9.4
Ross Burton (1):
asciidoc: update git repository
Sakib Sajal (1):
go: upgrade 1.16.13 -> 1.16.14
wangmy (1):
wireless-regdb: upgrade 2021.08.28 -> 2022.02.18
meta/lib/oeqa/selftest/cases/recipetool.py | 2 +-
.../go/{go-1.16.13.inc => go-1.16.14.inc} | 4 +-
...1.16.13.bb => go-binary-native_1.16.14.bb} | 4 +-
....16.13.bb => go-cross-canadian_1.16.14.bb} | 0
...o-cross_1.16.13.bb => go-cross_1.16.14.bb} | 0
...ssdk_1.16.13.bb => go-crosssdk_1.16.14.bb} | 0
...native_1.16.13.bb => go-native_1.16.14.bb} | 0
...ntime_1.16.13.bb => go-runtime_1.16.14.bb} | 0
.../go/{go_1.16.13.bb => go_1.16.14.bb} | 0
.../ruby/ruby/CVE-2021-31799.patch | 57 ----
.../ruby/ruby/CVE-2021-31810.patch | 258 ------------------
.../ruby/ruby/CVE-2021-32066.patch | 102 -------
.../ruby/{ruby_3.0.1.bb => ruby_3.0.3.bb} | 7 +-
meta/recipes-devtools/unfs3/unfs3_git.bb | 2 +-
.../asciidoc/asciidoc_9.1.0.bb | 2 +-
.../ghostscript/CVE-2021-45949.patch | 65 +++++
...tack-limits-after-function-evalution.patch | 51 ++++
.../ghostscript/ghostscript_9.53.3.bb | 2 +
.../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 +-
...ules_2.12.6.bb => lttng-modules_2.12.7.bb} | 2 +-
....08.28.bb => wireless-regdb_2022.02.18.bb} | 2 +-
...{libgcrypt_1.9.3.bb => libgcrypt_1.9.4.bb} | 2 +-
24 files changed, 148 insertions(+), 452 deletions(-)
rename meta/recipes-devtools/go/{go-1.16.13.inc => go-1.16.14.inc} (91%)
rename meta/recipes-devtools/go/{go-binary-native_1.16.13.bb => go-binary-native_1.16.14.bb} (83%)
rename meta/recipes-devtools/go/{go-cross-canadian_1.16.13.bb => go-cross-canadian_1.16.14.bb} (100%)
rename meta/recipes-devtools/go/{go-cross_1.16.13.bb => go-cross_1.16.14.bb} (100%)
rename meta/recipes-devtools/go/{go-crosssdk_1.16.13.bb => go-crosssdk_1.16.14.bb} (100%)
rename meta/recipes-devtools/go/{go-native_1.16.13.bb => go-native_1.16.14.bb} (100%)
rename meta/recipes-devtools/go/{go-runtime_1.16.13.bb => go-runtime_1.16.14.bb} (100%)
rename meta/recipes-devtools/go/{go_1.16.13.bb => go_1.16.14.bb} (100%)
delete mode 100644 meta/recipes-devtools/ruby/ruby/CVE-2021-31799.patch
delete mode 100644 meta/recipes-devtools/ruby/ruby/CVE-2021-31810.patch
delete mode 100644 meta/recipes-devtools/ruby/ruby/CVE-2021-32066.patch
rename meta/recipes-devtools/ruby/{ruby_3.0.1.bb => ruby_3.0.3.bb} (90%)
create mode 100644 meta/recipes-extended/ghostscript/ghostscript/CVE-2021-45949.patch
create mode 100644 meta/recipes-extended/ghostscript/ghostscript/check-stack-limits-after-function-evalution.patch
rename meta/recipes-kernel/lttng/{lttng-modules_2.12.6.bb => lttng-modules_2.12.7.bb} (94%)
rename meta/recipes-kernel/wireless-regdb/{wireless-regdb_2021.08.28.bb => wireless-regdb_2022.02.18.bb} (94%)
rename meta/recipes-support/libgcrypt/{libgcrypt_1.9.3.bb => libgcrypt_1.9.4.bb} (96%)
--
2.35.1
next reply other threads:[~2022-03-08 14:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 14:19 Anuj Mittal [this message]
2022-03-08 14:19 ` [hardknott][PATCH 01/15] go: upgrade 1.16.13 -> 1.16.14 Anuj Mittal
2022-03-08 14:19 ` [hardknott][PATCH 02/15] ruby : update to 3.0.3 Anuj Mittal
2022-03-08 14:19 ` [hardknott][PATCH 03/15] ghostscript: fix CVE-2021-45949 Anuj Mittal
2022-03-08 14:19 ` [hardknott][PATCH 04/15] libgcrypt: Upgrade 1.9.3 -> 1.9.4 Anuj Mittal
2022-03-08 14:19 ` [hardknott][PATCH 05/15] lttng-modules: upgrade 2.12.6 -> 2.12.7 Anuj Mittal
2022-03-08 14:19 ` [hardknott][PATCH 06/15] wireless-regdb: upgrade 2021.08.28 -> 2022.02.18 Anuj Mittal
2022-03-08 14:19 ` [hardknott][PATCH 07/15] selftest: recipetool: Correct the URI for socat Anuj Mittal
2022-03-08 14:19 ` [hardknott][PATCH 08/15] asciidoc: update git repository Anuj Mittal
2022-03-08 14:20 ` [hardknott][PATCH 09/15] linux-yocto/5.10: ppc/riscv: fix build with binutils 2.3.8 Anuj Mittal
2022-03-08 14:20 ` [hardknott][PATCH 10/15] linux-yocto/5.10: fix dssall build error " Anuj Mittal
2022-03-08 14:20 ` [hardknott][PATCH 11/15] linux-yocto/5.10: features/zram: remove CONFIG_ZRAM_DEF_COMP Anuj Mittal
2022-03-08 14:20 ` [hardknott][PATCH 12/15] linux-yocto/5.10: update to v5.10.101 Anuj Mittal
2022-03-08 14:20 ` [hardknott][PATCH 13/15] linux-yocto/5.10: Fix ramoops/ftrace Anuj Mittal
2022-03-08 14:20 ` [hardknott][PATCH 14/15] linux-yocto/5.10: update to v5.10.103 Anuj Mittal
2022-03-08 14:20 ` [hardknott][PATCH 15/15] unfs3: correct configure option Anuj Mittal
-- strict thread matches above, loose matches on Subject: below --
2022-01-21 14:50 [hardknott][PATCH 00/15] Patch review 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.1646748869.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.