From: bruce.ashfield@gmail.com
To: richard.purdie@linuxfoundation.org
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/6] kernel-yocto: consolidated pull request
Date: Mon, 4 Apr 2022 11:19:10 -0400 [thread overview]
Message-ID: <cover.1649085436.git.bruce.ashfield@gmail.com> (raw)
From: Bruce Ashfield <bruce.ashfield@gmail.com>
Richard,
A few aufs fixes, -stable and a configuration fixup for ARM/x86 split,
but otherwise, not a lot here.
I know the release is going to be cut shortly, so these can either be
post or in the release, obviously up to you. I'm sitting on other
changes that might cause issues, and will send them after the release.
Bruce
The following changes since commit 6459a06f2ed7d47f5df0c50d95e182e432311d53:
unzip: fix CVE-2021-4217 (2022-04-04 13:00:16 +0100)
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 (6):
linux-yocto/5.15: update to v5.15.32
linux-yocto/5.10: update to v5.10.109
linux-yocto/5.15: aufs: fixes and optimization
linux-yocto-rt/5.15: aufs: compile fix
linux-yocto/5.15: features/security: Move x86_64 configs to separate
file
linux-yocto/5.10: features/security: Move x86_64 configs to separate
file
.../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-04-04 18:46 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-04 15:19 bruce.ashfield [this message]
2022-04-04 15:19 ` [PATCH 1/6] linux-yocto/5.15: update to v5.15.32 bruce.ashfield
2022-04-04 15:19 ` [PATCH 2/6] linux-yocto/5.10: update to v5.10.109 bruce.ashfield
2022-04-04 15:19 ` [PATCH 3/6] linux-yocto/5.15: aufs: fixes and optimization bruce.ashfield
2022-04-04 15:19 ` [PATCH 4/6] linux-yocto-rt/5.15: aufs: compile fix bruce.ashfield
2022-04-04 15:19 ` [PATCH 5/6] linux-yocto/5.15: features/security: Move x86_64 configs to separate file bruce.ashfield
2022-04-04 19:20 ` Bruce Ashfield
[not found] ` <16E2C7C2E9968AA9.29157@lists.openembedded.org>
2022-04-04 21:38 ` [OE-core] " Bruce Ashfield
2022-04-04 15:19 ` [PATCH 6/6] linux-yocto/5.10: " bruce.ashfield
-- strict thread matches above, loose matches on Subject: below --
2025-07-08 14:36 [PATCH 0/6] kernel-yocto: consolidated pull request bruce.ashfield
2025-07-09 7:58 ` Richard Purdie
2025-07-09 13:01 ` Bruce Ashfield
2025-05-06 16:32 bruce.ashfield
2024-12-10 21:06 bruce.ashfield
2024-11-21 4:13 bruce.ashfield
2024-11-21 16:50 ` Richard Purdie
2021-07-29 4:49 Bruce Ashfield
2021-06-16 20:48 Bruce Ashfield
2017-07-11 15:04 Bruce Ashfield
2017-06-08 19:21 Bruce Ashfield
2016-08-15 18:26 Bruce Ashfield
2016-08-16 16:00 ` Burton, Ross
2016-08-16 16:01 ` Bruce Ashfield
2016-08-16 16:10 ` Burton, Ross
2016-08-16 16:11 ` Bruce Ashfield
2016-08-16 16:15 ` Burton, Ross
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.1649085436.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