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: Tue, 15 Nov 2022 19:38:18 -0500 [thread overview]
Message-ID: <cover.1668558954.git.bruce.ashfield@gmail.com> (raw)
From: Bruce Ashfield <bruce.ashfield@gmail.com>
Richard,
Here's the batched up -stable and -dev updates that I've been testing
for a while.
I've included both the 6.0 and 6.1 dev kernel updates, as both were
tested, and someone might want to use v6.0 as a development kernel,
and could use that commit as a baseline.
I ran into issues with devsrc and lttng-modules with 6.1, but have
all architectures working now. mips64 is throwing a trace on boot, but
I was able to complete testing. I'll revisit that later for 6.1+.
Cheers,
Bruce
The following changes since commit 44bb88cc869f3b42440d6f7aad000e706b739a2b:
mesa: do not rely on native llvm-config in target sysroot (2022-11-15 09:38:38 +0000)
are available in the Git repository at:
https://git.yoctoproject.org/poky-contrib zedd/kernel
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
Bruce Ashfield (10):
linux-yocto-dev: bump to v6.0+
linux-yocto/5.19: update to v5.19.16
linux-yocto/5.15: update to v5.15.74
linux-yocto/5.19: update to v5.19.17
linux-yocto/5.15: update to v5.15.76
linux-yocto/5.19: cfg: intel and vesa updates
kern-tools: integrate ZFS speedup patch
linux-yocto-dev: bump to v6.1
kernel-devsrc: fix for v6.1+
lttng-modules: fix build for v6.1+
.../kern-tools/kern-tools-native_git.bb | 2 +-
meta/recipes-kernel/linux/kernel-devsrc.bb | 25 +-
meta/recipes-kernel/linux/linux-yocto-dev.bb | 4 +-
.../linux/linux-yocto-rt_5.15.bb | 6 +-
.../linux/linux-yocto-rt_5.19.bb | 6 +-
.../linux/linux-yocto-tiny_5.15.bb | 6 +-
.../linux/linux-yocto-tiny_5.19.bb | 6 +-
meta/recipes-kernel/linux/linux-yocto_5.15.bb | 26 +-
meta/recipes-kernel/linux/linux-yocto_5.19.bb | 26 +-
...on-drop-kmem_alloc-avoid-dereferenci.patch | 278 ++++++++++++++++++
.../lttng/lttng-modules_2.13.7.bb | 1 +
11 files changed, 343 insertions(+), 43 deletions(-)
create mode 100644 meta/recipes-kernel/lttng/lttng-modules/0001-fix-mm-slab_common-drop-kmem_alloc-avoid-dereferenci.patch
--
2.19.1
next reply other threads:[~2022-11-16 0:38 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 0:38 bruce.ashfield [this message]
2022-11-16 0:38 ` [PATCH 01/10] linux-yocto-dev: bump to v6.0+ bruce.ashfield
2022-11-16 0:38 ` [PATCH 02/10] linux-yocto/5.19: update to v5.19.16 bruce.ashfield
2022-11-16 0:38 ` [PATCH 03/10] linux-yocto/5.15: update to v5.15.74 bruce.ashfield
2022-11-16 0:38 ` [PATCH 04/10] linux-yocto/5.19: update to v5.19.17 bruce.ashfield
2022-11-16 0:38 ` [PATCH 05/10] linux-yocto/5.15: update to v5.15.76 bruce.ashfield
2022-11-16 0:38 ` [PATCH 06/10] linux-yocto/5.19: cfg: intel and vesa updates bruce.ashfield
2022-11-16 0:38 ` [PATCH 07/10] kern-tools: integrate ZFS speedup patch bruce.ashfield
2022-11-16 0:38 ` [PATCH 08/10] linux-yocto-dev: bump to v6.1 bruce.ashfield
2022-11-16 0:38 ` [PATCH 09/10] kernel-devsrc: fix for v6.1+ bruce.ashfield
2022-11-16 8:24 ` [OE-core] " Alexander Kanavin
2022-11-16 13:26 ` Bruce Ashfield
2022-11-16 0:38 ` [PATCH 10/10] lttng-modules: fix build " bruce.ashfield
2022-11-16 21:31 ` [OE-core] [PATCH 00/10] kernel: consolidated pull request Alexandre Belloni
-- strict thread matches above, loose matches on Subject: below --
2023-09-29 20:04 bruce.ashfield
2023-09-30 11:07 ` 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
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.1668558954.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox