From: bruce.ashfield@gmail.com
To: richard.purdie@linuxfoundation.org
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH 00/10] linux-yocto: consolidated pull request
Date: Mon, 21 Aug 2023 11:44:35 -0400 [thread overview]
Message-ID: <cover.1692632563.git.bruce.ashfield@gmail.com> (raw)
From: Bruce Ashfield <bruce.ashfield@gmail.com>
Richard,
While we track down the remaining 6.4 boot issues, here is the
set of -stable and specific fixes that I've queued in my kernel
testing tree.
It is possible that some of the 6.4-stable's have fixes for our
boot issues, but I didn't see anything obvious.
In particular we have the -rt warning fix from PaulG and also
a fixup on our isocpus patch.
Cheers,
Bruce
The following changes since commit 37ebe9907ac5639bc200ae50d0d79b14a790ab55:
oeqa/runtime/rust: correct rust test (2023-08-21 16:15:35 +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.1: update to v6.1.44
linux-yocto/6.4: update to v6.4.10
linux-yocto/6.1: update to v6.1.45
kern-tools: include utility to post process config diffs
linux-yocto/6.1: fix uninitialized read in nohz_full/isolcpus setup
linux-yocto/6.4: fix uninitialized read in nohz_full/isolcpus setup
linux-yocto/6.4: update to v6.4.11
linux-yocto/6.1: update to v6.1.46
linux-yocto/6.1: fix IRQ-80 warnings
linux-yocto/6.4: fix IRQ-80 warnings
.../kern-tools/kern-tools-native_git.bb | 2 +-
.../linux/linux-yocto-rt_6.1.bb | 6 ++--
.../linux/linux-yocto-rt_6.4.bb | 6 ++--
.../linux/linux-yocto-tiny_6.1.bb | 6 ++--
.../linux/linux-yocto-tiny_6.4.bb | 6 ++--
meta/recipes-kernel/linux/linux-yocto_6.1.bb | 28 +++++++++----------
meta/recipes-kernel/linux/linux-yocto_6.4.bb | 28 +++++++++----------
7 files changed, 41 insertions(+), 41 deletions(-)
--
2.34.1
next reply other threads:[~2023-08-21 15:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-21 15:44 bruce.ashfield [this message]
2023-08-21 15:44 ` [PATCH 01/10] linux-yocto/6.1: update to v6.1.44 bruce.ashfield
2023-08-21 15:44 ` [PATCH 02/10] linux-yocto/6.4: update to v6.4.10 bruce.ashfield
2023-08-21 15:44 ` [PATCH 03/10] linux-yocto/6.1: update to v6.1.45 bruce.ashfield
2023-08-21 15:44 ` [PATCH 04/10] kern-tools: include utility to post process config diffs bruce.ashfield
2023-08-21 15:44 ` [PATCH 05/10] linux-yocto/6.1: fix uninitialized read in nohz_full/isolcpus setup bruce.ashfield
2023-08-21 15:44 ` [PATCH 06/10] linux-yocto/6.4: " bruce.ashfield
2023-08-21 15:44 ` [PATCH 07/10] linux-yocto/6.4: update to v6.4.11 bruce.ashfield
2023-08-21 15:44 ` [PATCH 08/10] linux-yocto/6.1: update to v6.1.46 bruce.ashfield
2023-08-21 15:44 ` [PATCH 09/10] linux-yocto/6.1: fix IRQ-80 warnings bruce.ashfield
2023-08-21 15:44 ` [PATCH 10/10] linux-yocto/6.4: " bruce.ashfield
2023-08-21 15:47 ` [PATCH 00/10] linux-yocto: consolidated pull request Richard Purdie
2023-08-21 15:50 ` Bruce Ashfield
2023-08-22 7:13 ` [OE-core] " Luca Ceresoli
2023-08-22 7:44 ` Mikko Rapeli
2023-08-22 12:47 ` Bruce Ashfield
-- strict thread matches above, loose matches on Subject: below --
2022-07-14 19:14 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.1692632563.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