From: "Bruce Ashfield" <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: Wed, 16 Jun 2021 16:48:48 -0400 [thread overview]
Message-ID: <cover.1623876372.git.bruce.ashfield@gmail.com> (raw)
From: Bruce Ashfield <bruce.ashfield@gmail.com>
Richard,
Here's my queued set of update to linux -yocto. These are -stable, and of
course the AB INT fix provided by paulg.
The other change is one to the -dev kernel that allows the single AUTOREV
recipe to continue to work in older releases as we march through newer
kernels in master. Some users ran into this problem recently, and have
tested/confirmed the fix. There's no change to anyone but a linux-yocto-dev
kernel consumer.
Cheers,
Bruce
The following changes since commit 682ddc5f2a2493e5c7760c0745dacd24fe975479:
releases: put release number after "Release Series" (2021-06-14 22:45:33 +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-dev: base AUTOREV on specified version
linux-yocto/5.4: update to v5.4.124
linux-yocto/5.10: restore aufs
linux-yocto/5.10: update to v5.10.43
linux-yocto/5.4: update to v5.4.125
linux-yocto/5.10: cgroup1: fix leaked context root causing sporadic
NULL deref in LTP
meta/classes/kernel-yocto.bbclass | 24 +++++++++++++++++++
.../linux/linux-yocto-rt_5.10.bb | 6 ++---
.../linux/linux-yocto-rt_5.4.bb | 6 ++---
.../linux/linux-yocto-tiny_5.10.bb | 8 +++----
.../linux/linux-yocto-tiny_5.4.bb | 8 +++----
meta/recipes-kernel/linux/linux-yocto_5.10.bb | 24 +++++++++----------
meta/recipes-kernel/linux/linux-yocto_5.4.bb | 22 ++++++++---------
7 files changed, 61 insertions(+), 37 deletions(-)
--
2.19.1
next reply other threads:[~2021-06-16 20:48 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-16 20:48 Bruce Ashfield [this message]
2021-06-16 20:48 ` [PATCH 1/6] linux-yocto-dev: base AUTOREV on specified version Bruce Ashfield
2021-07-05 13:52 ` Bruce Ashfield
2021-07-06 2:49 ` Anuj Mittal
2021-07-06 2:53 ` Bruce Ashfield
2021-07-08 6:29 ` [OE-core] " Anuj Mittal
2021-06-16 20:48 ` [PATCH 2/6] linux-yocto/5.4: update to v5.4.124 Bruce Ashfield
2021-06-16 20:48 ` [PATCH 3/6] linux-yocto/5.10: restore aufs Bruce Ashfield
2021-06-16 20:48 ` [PATCH 4/6] linux-yocto/5.10: update to v5.10.43 Bruce Ashfield
2021-06-16 20:48 ` [PATCH 5/6] linux-yocto/5.4: update to v5.4.125 Bruce Ashfield
2021-06-16 20:48 ` [PATCH 6/6] linux-yocto/5.10: cgroup1: fix leaked context root causing sporadic NULL deref in LTP 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
2022-04-04 15:19 bruce.ashfield
2021-07-29 4:49 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.1623876372.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