From: bruce.ashfield@gmail.com
To: richard.purdie@linuxfoundation.org
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH 00/10] kernel: consolidated pull request
Date: Fri, 29 Sep 2023 16:04:44 -0400 [thread overview]
Message-ID: <cover.1696017123.git.bruce.ashfield@gmail.com> (raw)
From: Bruce Ashfield <bruce.ashfield@gmail.com>
Richard,
Given where we are in the release cycle, this clearly is NOT a typical
consolidated pull request.
I've done what normally takes about three weeks in about 4 days.
With 6.4 going EOL before expected upstream, it really isn't a suitable
reference kernel for the release.
So we've decided to take on the task of getting 6.5 ready and available,
and at the same time moving the -dev kernel to v6.6. The -dev kernel
testing for 6.5 was critical for this, since I already knew the core
was sane.
Also we've never shipped purposely mismatched libc-headers in the release,
so I also took the leap to update the libc-headers to match.
I've already sent fixes to meta-oe, and there's a btrfs update in this
series to fix breakage that I found in the tightly coupled packages.
I've built and booted core-image-kernel-dev, core-image-minimal, core-image-sato
for both glibc and musl for all the supported architectures.
There will be some things that break regardless, but this needs the
better coverage of the AB.
If this causes too much problems, our choices are to ship 6.4 EOLd, or
fall all the way back to 6.1.
I'll remove 6.4 from master once we've figured out the fallout from
this kernel, and which direction we are going.
Cheers,
Bruce
The following changes since commit d4f2f8269cff0e4e9a98ad1ef9c0f7b8a909d563:
recipetool/devtool: Ensure server knows about changed files (2023-09-18 11:35:38 +0100)
are available in the Git repository at:
https://git.yoctoproject.org/poky-contrib zedd/kernel
https://git.yoctoproject.org/poky-contrib/log/?h=zedd/kernel
Bruce Ashfield (10):
linux-yocto/6.4: update to v6.4.15
linux-yocto/6.1: update to v6.1.52
linux-yocto/6.4: update to v6.4.16
linux-yocto/6.1: update to v6.1.53
linux-yocto/6.1: update to v6.1.55
linux-yocto-dev: update to v6.6-rcX
linux-yocto: introduce 6.5 reference kernel recipes
linux-libc-headers: uprev to v6.5
linux-libc-headers: default to 6.5
btrfs-progs: update to version v6.5.1
meta/conf/distro/include/tcmode-default.inc | 2 +-
...fs-tools_6.3.3.bb => btrfs-tools_6.5.1.bb} | 2 +-
...aders_6.4.bb => linux-libc-headers_6.5.bb} | 2 +-
.../linux/cve-exclusion_6.1.inc | 54 +-
.../linux/cve-exclusion_6.4.inc | 36 +-
.../linux/cve-exclusion_6.5.inc | 5072 +++++++++++++++++
meta/recipes-kernel/linux/linux-yocto-dev.bb | 4 +-
.../linux/linux-yocto-rt_6.1.bb | 6 +-
.../linux/linux-yocto-rt_6.4.bb | 6 +-
.../linux/linux-yocto-rt_6.5.bb | 48 +
.../linux/linux-yocto-tiny_6.1.bb | 6 +-
.../linux/linux-yocto-tiny_6.4.bb | 6 +-
.../linux/linux-yocto-tiny_6.5.bb | 33 +
meta/recipes-kernel/linux/linux-yocto_6.1.bb | 28 +-
meta/recipes-kernel/linux/linux-yocto_6.4.bb | 28 +-
meta/recipes-kernel/linux/linux-yocto_6.5.bb | 72 +
16 files changed, 5343 insertions(+), 62 deletions(-)
rename meta/recipes-devtools/btrfs-tools/{btrfs-tools_6.3.3.bb => btrfs-tools_6.5.1.bb} (98%)
rename meta/recipes-kernel/linux-libc-headers/{linux-libc-headers_6.4.bb => linux-libc-headers_6.5.bb} (83%)
create mode 100644 meta/recipes-kernel/linux/cve-exclusion_6.5.inc
create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_6.5.bb
create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_6.5.bb
create mode 100644 meta/recipes-kernel/linux/linux-yocto_6.5.bb
--
2.34.1
next reply other threads:[~2023-09-29 20:05 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-29 20:04 bruce.ashfield [this message]
2023-09-29 20:04 ` [PATCH 01/10] linux-yocto/6.4: update to v6.4.15 bruce.ashfield
2023-09-29 20:04 ` [PATCH 02/10] linux-yocto/6.1: update to v6.1.52 bruce.ashfield
2023-09-29 20:04 ` [PATCH 03/10] linux-yocto/6.4: update to v6.4.16 bruce.ashfield
2023-09-29 20:04 ` [PATCH 04/10] linux-yocto/6.1: update to v6.1.53 bruce.ashfield
2023-09-29 20:04 ` [PATCH 05/10] linux-yocto/6.1: update to v6.1.55 bruce.ashfield
2023-09-29 20:04 ` [PATCH 06/10] linux-yocto-dev: update to v6.6-rcX bruce.ashfield
2023-09-29 20:04 ` [PATCH 07/10] linux-yocto: introduce 6.5 reference kernel recipes bruce.ashfield
2023-09-29 20:04 ` [PATCH 08/10] linux-libc-headers: uprev to v6.5 bruce.ashfield
2023-09-29 20:04 ` [PATCH 09/10] linux-libc-headers: default to 6.5 bruce.ashfield
2023-09-29 20:04 ` [PATCH 10/10] btrfs-progs: update to version v6.5.1 bruce.ashfield
2023-09-30 11:07 ` [PATCH 00/10] kernel: consolidated pull request Richard Purdie
2023-09-30 16:33 ` Bruce Ashfield
2023-09-30 16:58 ` Richard Purdie
2023-09-30 17:05 ` Bruce Ashfield
2023-09-30 17:26 ` Richard Purdie
2023-10-01 10:13 ` Richard Purdie
2023-10-01 11:49 ` Richard Purdie
2023-10-01 14:58 ` Bruce Ashfield
2023-10-01 15:06 ` Bruce Ashfield
2023-10-01 17:40 ` [OE-core] " Khem Raj
2023-10-01 21:30 ` Khem Raj
[not found] ` <1789F42963592BBC.31348@lists.openembedded.org>
2023-10-01 13:20 ` Richard Purdie
-- strict thread matches above, loose matches on Subject: below --
2022-11-16 0:38 bruce.ashfield
2022-01-11 17:59 bruce.ashfield
2022-01-11 21:38 ` Richard Purdie
2021-04-19 0:06 Bruce Ashfield
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.1696017123.git.bruce.ashfield@gmail.com \
--to=bruce.ashfield@gmail.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 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.