From: "Steve Sakoman" <steve@sakoman.com>
To: openembedded-core@lists.openembedded.org
Subject: [OE-core][dunfell 0/7] Patch review
Date: Mon, 17 Aug 2020 05:11:44 -1000 [thread overview]
Message-ID: <cover.1597676744.git.steve@sakoman.com> (raw)
Please review this next set of patches for dunfell and have comments back
by end of day Wednesday.
Passed a-full on autobuilder (other than 500 server error posting report for qemumips-alt):
https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/1265
The following changes since commit b95d6aeafb70765e22d2e1254e749a48f508d489:
uninative: Handle PREMIRRORS generically (2020-08-09 09:26:54 -1000)
are available in the Git repository at:
git://git.openembedded.org/openembedded-core-contrib stable/dunfell-nut
http://cgit.openembedded.org/openembedded-core-contrib/log/?h=stable/dunfell-nut
Bruce Ashfield (3):
linux-yocto-rt/5.4: update to rt32
linux-yocto/5.4: update to v5.4.56
linux-yocto/5.4: update to v5.4.57
Khem Raj (4):
glibc: Bring in CVE fixes and other bugfixes from 2.31 release branch
gcc-9.3.inc: Mark CVE-2019-15847 as fixed
go: update 1.14.4 -> 1.14.6
go: Upgrade to 1.14.7
meta/recipes-core/glibc/glibc-version.inc | 2 +-
.../glibc/0016-Add-unused-attribute.patch | 31 ---
.../glibc/glibc/CVE-2020-6096.patch | 112 ----------
.../glibc/glibc/CVE-2020-6096_2.patch | 194 ------------------
meta/recipes-core/glibc/glibc_2.31.bb | 5 +-
meta/recipes-devtools/gcc/gcc-9.3.inc | 2 +
meta/recipes-devtools/go/go-1.14.inc | 5 +-
.../linux/linux-yocto-rt_5.4.bb | 6 +-
.../linux/linux-yocto-tiny_5.4.bb | 8 +-
meta/recipes-kernel/linux/linux-yocto_5.4.bb | 22 +-
10 files changed, 24 insertions(+), 363 deletions(-)
delete mode 100644 meta/recipes-core/glibc/glibc/0016-Add-unused-attribute.patch
delete mode 100644 meta/recipes-core/glibc/glibc/CVE-2020-6096.patch
delete mode 100644 meta/recipes-core/glibc/glibc/CVE-2020-6096_2.patch
--
2.17.1
next reply other threads:[~2020-08-17 15:12 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-17 15:11 Steve Sakoman [this message]
2020-08-17 15:11 ` [OE-core][dunfell 1/7] glibc: Bring in CVE fixes and other bugfixes from 2.31 release branch Steve Sakoman
2020-08-17 15:11 ` [OE-core][dunfell 2/7] gcc-9.3.inc: Mark CVE-2019-15847 as fixed Steve Sakoman
2020-08-17 15:11 ` [OE-core][dunfell 3/7] go: update 1.14.4 -> 1.14.6 Steve Sakoman
2020-08-17 15:11 ` [OE-core][dunfell 4/7] go: Upgrade to 1.14.7 Steve Sakoman
2020-08-17 15:11 ` [OE-core][dunfell 5/7] linux-yocto-rt/5.4: update to rt32 Steve Sakoman
2020-08-17 15:11 ` [OE-core][dunfell 6/7] linux-yocto/5.4: update to v5.4.56 Steve Sakoman
2020-08-17 15:11 ` [OE-core][dunfell 7/7] linux-yocto/5.4: update to v5.4.57 Steve Sakoman
-- strict thread matches above, loose matches on Subject: below --
2020-09-18 16:15 [OE-core][dunfell 0/7] Patch review Steve Sakoman
2021-07-15 14:07 Steve Sakoman
2021-07-15 14:16 ` Andrej Valek
2022-03-30 2:27 Steve Sakoman
2022-07-29 15:24 Steve Sakoman
2022-09-08 2:28 Steve Sakoman
2022-10-24 14:24 Steve Sakoman
2022-12-01 15:25 Steve Sakoman
2023-04-04 2:39 Steve Sakoman
2023-04-22 15:57 Steve Sakoman
2023-05-11 21:28 Steve Sakoman
2023-09-26 14:12 Steve Sakoman
2024-02-13 21:43 Steve Sakoman
2024-04-03 3:11 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.1597676744.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