From: bruce.ashfield@gmail.com
To: richard.purdie@linuxfoundation.org
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/8] linux-yocto: consolidated pull request
Date: Tue, 5 Sep 2023 10:37:06 -0400 [thread overview]
Message-ID: <cover.1693924532.git.bruce.ashfield@gmail.com> (raw)
From: Bruce Ashfield <bruce.ashfield@gmail.com>
Richard,
Here's the next round of -stable and configuration changes.
I also ran into a build issue with 6.4+ on one of my builders
due to a gzip mismatch with zlib versions. So I've included
a fix for that.
Cheers,
Bruce
The following changes since commit 733afeffd19a2ae3af34abe95e514cb4b99cd366:
bitbake: server/process: Add more timing debug (2023-09-05 08:14:50 +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 (8):
linux-yocto/6.4: fix CONFIG_F2FS_IO_TRACE configuration warning
linux-yocto/6.1: fix CONFIG_F2FS_IO_TRACE configuration warning
linux-yocto/6.4: update to v6.4.12
linux-yocto/6.1: update to v6.1.50
linux-yocto/6.4: update to v6.4.13
linux-yocto/6.4: update to v6.4.14
linux-yocto/6.1: update to v6.1.51
linux-yocto: add gzip-native to DEPENDS
.../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.inc | 2 +-
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-09-05 14:37 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-05 14:37 bruce.ashfield [this message]
2023-09-05 14:37 ` [PATCH 1/8] linux-yocto/6.4: fix CONFIG_F2FS_IO_TRACE configuration warning bruce.ashfield
2023-09-05 14:37 ` [PATCH 2/8] linux-yocto/6.1: " bruce.ashfield
2023-09-05 14:37 ` [PATCH 3/8] linux-yocto/6.4: update to v6.4.12 bruce.ashfield
2023-09-05 14:37 ` [PATCH 4/8] linux-yocto/6.1: update to v6.1.50 bruce.ashfield
2023-09-05 14:37 ` [PATCH 5/8] linux-yocto/6.4: update to v6.4.13 bruce.ashfield
2023-09-05 14:37 ` [PATCH 6/8] linux-yocto/6.4: update to v6.4.14 bruce.ashfield
2023-09-05 14:37 ` [PATCH 7/8] linux-yocto/6.1: update to v6.1.51 bruce.ashfield
2023-09-05 14:37 ` [PATCH 8/8] linux-yocto: add gzip-native to DEPENDS bruce.ashfield
2023-09-05 15:01 ` Richard Purdie
2023-09-05 15:02 ` Bruce Ashfield
[not found] ` <178208DA97C569CC.31888@lists.openembedded.org>
2023-09-05 15:07 ` [OE-core] " Bruce Ashfield
2023-09-06 12:39 ` [OE-core] [PATCH 0/8] linux-yocto: consolidated pull request Ross Burton
2023-09-06 12:56 ` Bruce Ashfield
2023-09-06 13:15 ` Ross Burton
-- strict thread matches above, loose matches on Subject: below --
2023-03-01 15:13 bruce.ashfield
2021-07-15 19:30 Bruce Ashfield
2021-07-02 15:13 Bruce Ashfield
2021-07-03 22:02 ` Richard Purdie
2021-07-04 2:43 ` Bruce Ashfield
2021-02-03 3:23 [PATCH 0/8]: " Bruce Ashfield
2019-03-25 3:11 [PATCH 0/8] " bruce.ashfield
2016-12-08 17:58 Bruce Ashfield
2016-06-28 2:40 Bruce Ashfield
2016-04-02 0:09 Bruce Ashfield
2015-02-06 16:31 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.1693924532.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