From: Steve Sakoman <steve@sakoman.com>
To: openembedded-core@lists.openembedded.org
Subject: [OE-core][dunfell 00/11] Pull request (cover letter only)
Date: Thu, 29 Sep 2022 16:38:37 -1000 [thread overview]
Message-ID: <cover.1664505370.git.steve@sakoman.com> (raw)
The following changes since commit ef38f7acee3f0ae400138fa60f4695a86dffc16e:
linux-yocto/5.4: update to v5.4.213 (2022-09-22 04:40:18 -1000)
are available in the Git repository at:
https://git.openembedded.org/openembedded-core-contrib stable/dunfell-next
http://cgit.openembedded.org/openembedded-core-contrib/log/?h=stable/dunfell-next
Dmitry Baryshkov (3):
linux-firmware: upgrade 20220708 -> 20220913
linux-firmware: package new Qualcomm firmware
linux-firmware: package new Qualcomm firmware
Hitendra Prajapati (2):
bluez: CVE-2022-39176 BlueZ allows physically proximate attackers
golang: CVE-2022-27664 net/http: handle server errors after sending
GOAWAY
Martin Jansa (1):
create-pull-request: don't switch the git remote protocol to git://
Minjae Kim (1):
inetutils: CVE-2022-39028 - fix remote DoS vulnerability in
inetutils-telnetd
Richard Purdie (2):
vim: Upgrade 9.0.453 -> 9.0.541
vim: Upgrade 9.0.0541 -> 9.0.0598
Robert Joslyn (1):
tzdata: Update from 2022b to 2022c
Shubham Kulkarni (1):
go: Add fix for CVE-2022-32190
meta/recipes-connectivity/bluez5/bluez5.inc | 1 +
.../bluez5/bluez5/CVE-2022-39176.patch | 126 ++++++++++++++++++
.../inetutils/inetutils/CVE-2022-39028.patch | 54 ++++++++
.../inetutils/inetutils_1.9.4.bb | 1 +
meta/recipes-devtools/go/go-1.14.inc | 5 +
.../go/go-1.14/0001-CVE-2022-32190.patch | 74 ++++++++++
.../go/go-1.14/0002-CVE-2022-32190.patch | 48 +++++++
.../go/go-1.14/0003-CVE-2022-32190.patch | 36 +++++
.../go/go-1.14/0004-CVE-2022-32190.patch | 82 ++++++++++++
.../go/go-1.14/CVE-2022-27664.patch | 68 ++++++++++
meta/recipes-extended/timezone/timezone.inc | 6 +-
...20220708.bb => linux-firmware_20220913.bb} | 39 +++++-
meta/recipes-support/vim/vim.inc | 4 +-
scripts/create-pull-request | 2 +-
14 files changed, 536 insertions(+), 10 deletions(-)
create mode 100644 meta/recipes-connectivity/bluez5/bluez5/CVE-2022-39176.patch
create mode 100644 meta/recipes-connectivity/inetutils/inetutils/CVE-2022-39028.patch
create mode 100644 meta/recipes-devtools/go/go-1.14/0001-CVE-2022-32190.patch
create mode 100644 meta/recipes-devtools/go/go-1.14/0002-CVE-2022-32190.patch
create mode 100644 meta/recipes-devtools/go/go-1.14/0003-CVE-2022-32190.patch
create mode 100644 meta/recipes-devtools/go/go-1.14/0004-CVE-2022-32190.patch
create mode 100644 meta/recipes-devtools/go/go-1.14/CVE-2022-27664.patch
rename meta/recipes-kernel/linux-firmware/{linux-firmware_20220708.bb => linux-firmware_20220913.bb} (94%)
--
2.25.1
next reply other threads:[~2022-09-30 2:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-30 2:38 Steve Sakoman [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-11-16 14:10 [OE-core][dunfell 00/11] Pull request (cover letter only) Steve Sakoman
2022-08-21 23:03 Steve Sakoman
2022-08-12 21:11 Steve Sakoman
2022-06-03 23:30 Steve Sakoman
2022-04-20 2:42 Steve Sakoman
2022-01-24 22:32 Steve Sakoman
2022-01-18 22:23 Steve Sakoman
2021-04-22 16:04 Steve Sakoman
2020-08-07 16:39 Steve Sakoman
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.1664505370.git.steve@sakoman.com \
--to=steve@sakoman.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