From: bruce.ashfield@gmail.com
To: richard.purdie@linuxfoundation.org
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/9] linux-yocto: consolidated pull request
Date: Fri, 4 Mar 2022 20:25:08 -0500 [thread overview]
Message-ID: <cover.1646443420.git.bruce.ashfield@gmail.com> (raw)
From: Bruce Ashfield <bruce.ashfield@gmail.com>
Richard,
Here's the next round of -stable and configuration updates for 5.10 and
5.15.
Nothing significant here, I've been soaking them for a while, hopefully
the AB agrees with my "it's green" assesment!
Cheers,
Bruce
The following changes since commit a25c07622502727ca1b0e01d32127b57f75d28fb:
Revert "libsdl2: Add libunwind-native to the libsdl2-native DEPENDS" (2022-03-05 00:08:33 +0000)
are available in the Git repository at:
git://git.yoctoproject.org/poky-contrib zedd/kernel
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
Bruce Ashfield (9):
linux-yocto/5.15: riscv64: drop MAXPHYSMEM_128GB
linux-yocto/5.10: features/zram: remove CONFIG_ZRAM_DEF_COMP
linux-yocto/5.15: update to v5.15.24
linux-yocto/5.10: update to v5.10.101
linux-yocto/5.10: Fix ramoops/ftrace
linux-yocto/5.15: arm defconfig fixes
linux-yocto/5.15: update to v5.15.26
linux-yocto/5.10: update to v5.10.103
linux-yocto/5.15: riscv32: drop MAXPHYSMEM_1GB
.../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 | 8 +++---
meta/recipes-kernel/linux/linux-yocto_5.10.bb | 24 ++++++++---------
meta/recipes-kernel/linux/linux-yocto_5.15.bb | 26 +++++++++----------
6 files changed, 39 insertions(+), 39 deletions(-)
--
2.19.1
next reply other threads:[~2022-03-05 1:25 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-05 1:25 bruce.ashfield [this message]
2022-03-05 1:25 ` [PATCH 1/9] linux-yocto/5.15: riscv64: drop MAXPHYSMEM_128GB bruce.ashfield
2022-03-05 1:25 ` [PATCH 2/9] linux-yocto/5.10: features/zram: remove CONFIG_ZRAM_DEF_COMP bruce.ashfield
2022-03-05 1:25 ` [PATCH 3/9] linux-yocto/5.15: update to v5.15.24 bruce.ashfield
2022-03-05 1:25 ` [PATCH 4/9] linux-yocto/5.10: update to v5.10.101 bruce.ashfield
2022-03-05 1:25 ` [PATCH 5/9] linux-yocto/5.10: Fix ramoops/ftrace bruce.ashfield
2022-03-05 1:25 ` [PATCH 6/9] linux-yocto/5.15: arm defconfig fixes bruce.ashfield
2022-03-05 1:25 ` [PATCH 7/9] linux-yocto/5.15: update to v5.15.26 bruce.ashfield
2022-03-05 1:25 ` [PATCH 8/9] linux-yocto/5.10: update to v5.10.103 bruce.ashfield
2022-03-05 1:25 ` [PATCH 9/9] linux-yocto/5.15: riscv32: drop MAXPHYSMEM_1GB bruce.ashfield
-- strict thread matches above, loose matches on Subject: below --
2024-03-19 23:01 [PATCH 0/9] linux-yocto: consolidated pull request bruce.ashfield
2019-05-30 12:44 bruce.ashfield
2019-05-31 8:01 ` richard.purdie
2019-05-31 12:53 ` Bruce Ashfield
2019-05-31 13:22 ` richard.purdie
2019-05-31 13:46 ` Bruce Ashfield
2019-05-31 17:07 ` richard.purdie
2019-05-31 21:31 ` Bruce Ashfield
2017-12-21 15:49 Bruce Ashfield
2016-07-13 1:19 Bruce Ashfield
2016-03-30 12:24 Bruce Ashfield
2012-06-07 19:59 Bruce Ashfield
2012-06-08 10:58 ` Richard Purdie
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.1646443420.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