From: Steve Sakoman <steve@sakoman.com>
To: openembedded-core@lists.openembedded.org
Subject: [OE-core][kirkstone 00/23] Patch review
Date: Sun, 17 Jul 2022 14:30:01 -1000 [thread overview]
Message-ID: <cover.1658093505.git.steve@sakoman.com> (raw)
Please review this set of patches for kirkstone and have comments back by
end of day Tuesday.
Passed a-full on autobuilder:
https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/3924
The following changes since commit a4bfb5ceb5cf8c0c6d27225b27ef10c0b9dceccb:
libsoup: upgrade 3.0.6 -> 3.0.7 (2022-07-13 11:54:16 -1000)
are available in the Git repository at:
git://git.openembedded.org/openembedded-core-contrib stable/kirkstone-nut
http://cgit.openembedded.org/openembedded-core-contrib/log/?h=stable/kirkstone-nut
Bruce Ashfield (19):
linux-yocto/5.10: update to v5.10.121
linux-yocto/5.10: update to v5.10.123
linux-yocto/5.10: update to v5.10.128
linux-yocto/5.10: fix build_OID_registry/conmakehash buildpaths
warning
linux-yocto/5.10: fix buildpaths issue with gen-mach-types
linux-yocto/5.10: update to v5.10.130
linux-yocto/5.10: fix buildpaths issue with pnmtologo
linux-yocto/5.15: update to v5.15.46
linux-yocto/5.15: update to v5.15.48
linux-yocto/5.15: drop obselete GPIO sysfs ABI
linux-yocto/5.15: update to v5.15.52
linux-yocto/5.15: fix qemuppc buildpaths warning
linux-yocto/5.15: fix build_OID_registry buildpaths warning
linux-yocto/5.15: fix buildpaths issue with gen-mach-types
linux-yocto/5.15: update to v5.15.54
linux-yocto/5.15: fix buildpaths issue with pnmtologo
kernel-devsrc: fix reproducibility and buildpaths QA warning
kernel-devsrc: ppc32: fix reproducibility
perf: fix reproducibility in 5.19+
Richard Purdie (4):
qemu: Fix slirp determinism issue
qemu: Add PACKAGECONFIG for brlapi
gperf: Add a patch to work around reproducibility issues
gperf: Switch to upstream patch
.../qemu/qemu-system-native_6.2.0.bb | 2 +-
meta/recipes-devtools/qemu/qemu.inc | 2 +
meta/recipes-devtools/qemu/qemu_6.2.0.bb | 4 +-
...c6e57a308a05889c80c048dbc58bdc378dcb.patch | 181 ++++++++++++++++++
meta/recipes-extended/gperf/gperf_3.1.bb | 2 +
meta/recipes-kernel/linux/kernel-devsrc.bb | 8 +-
.../linux/linux-yocto-rt_5.10.bb | 6 +-
.../linux/linux-yocto-rt_5.15.bb | 6 +-
.../linux/linux-yocto-tiny_5.10.bb | 8 +-
.../linux/linux-yocto-tiny_5.15.bb | 6 +-
meta/recipes-kernel/linux/linux-yocto_5.10.bb | 24 +--
meta/recipes-kernel/linux/linux-yocto_5.15.bb | 26 +--
meta/recipes-kernel/perf/perf.bb | 6 +
13 files changed, 238 insertions(+), 43 deletions(-)
create mode 100644 meta/recipes-extended/gperf/gperf/1862c6e57a308a05889c80c048dbc58bdc378dcb.patch
--
2.25.1
next reply other threads:[~2022-07-18 0:30 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-18 0:30 Steve Sakoman [this message]
2022-07-18 0:30 ` [OE-core][kirkstone 01/23] qemu: Fix slirp determinism issue Steve Sakoman
2022-07-18 0:30 ` [OE-core][kirkstone 02/23] qemu: Add PACKAGECONFIG for brlapi Steve Sakoman
2022-07-18 0:30 ` [OE-core][kirkstone 03/23] linux-yocto/5.10: update to v5.10.121 Steve Sakoman
2022-07-18 0:30 ` [OE-core][kirkstone 04/23] linux-yocto/5.10: update to v5.10.123 Steve Sakoman
2022-07-18 0:30 ` [OE-core][kirkstone 05/23] linux-yocto/5.10: update to v5.10.128 Steve Sakoman
2022-07-18 0:30 ` [OE-core][kirkstone 06/23] linux-yocto/5.10: fix build_OID_registry/conmakehash buildpaths warning Steve Sakoman
2022-07-18 0:30 ` [OE-core][kirkstone 07/23] linux-yocto/5.10: fix buildpaths issue with gen-mach-types Steve Sakoman
2022-07-18 0:30 ` [OE-core][kirkstone 08/23] linux-yocto/5.10: update to v5.10.130 Steve Sakoman
2022-07-18 0:30 ` [OE-core][kirkstone 09/23] linux-yocto/5.10: fix buildpaths issue with pnmtologo Steve Sakoman
2022-07-18 0:30 ` [OE-core][kirkstone 10/23] linux-yocto/5.15: update to v5.15.46 Steve Sakoman
2022-07-18 0:30 ` [OE-core][kirkstone 11/23] linux-yocto/5.15: update to v5.15.48 Steve Sakoman
2022-07-18 0:30 ` [OE-core][kirkstone 12/23] linux-yocto/5.15: drop obselete GPIO sysfs ABI Steve Sakoman
2022-07-18 0:30 ` [OE-core][kirkstone 13/23] linux-yocto/5.15: update to v5.15.52 Steve Sakoman
2022-07-18 0:30 ` [OE-core][kirkstone 14/23] linux-yocto/5.15: fix qemuppc buildpaths warning Steve Sakoman
2022-07-18 0:30 ` [OE-core][kirkstone 15/23] linux-yocto/5.15: fix build_OID_registry " Steve Sakoman
2022-07-18 0:30 ` [OE-core][kirkstone 16/23] linux-yocto/5.15: fix buildpaths issue with gen-mach-types Steve Sakoman
2022-07-18 0:30 ` [OE-core][kirkstone 17/23] linux-yocto/5.15: update to v5.15.54 Steve Sakoman
2022-07-18 0:30 ` [OE-core][kirkstone 18/23] linux-yocto/5.15: fix buildpaths issue with pnmtologo Steve Sakoman
2022-07-18 0:30 ` [OE-core][kirkstone 19/23] kernel-devsrc: fix reproducibility and buildpaths QA warning Steve Sakoman
2022-07-18 0:30 ` [OE-core][kirkstone 20/23] kernel-devsrc: ppc32: fix reproducibility Steve Sakoman
2022-07-18 0:30 ` [OE-core][kirkstone 21/23] gperf: Add a patch to work around reproducibility issues Steve Sakoman
2022-07-18 0:30 ` [OE-core][kirkstone 22/23] gperf: Switch to upstream patch Steve Sakoman
2022-07-18 0:30 ` [OE-core][kirkstone 23/23] perf: fix reproducibility in 5.19+ Steve Sakoman
-- strict thread matches above, loose matches on Subject: below --
2022-12-01 14:26 [OE-core][kirkstone 00/23] Patch review Steve Sakoman
2023-02-21 14:40 Steve Sakoman
2024-05-09 12:04 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.1658093505.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 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.