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: Thu, 29 Jul 2021 00:49:57 -0400 [thread overview]
Message-ID: <cover.1627533955.git.bruce.ashfield@gmail.com> (raw)
From: Bruce Ashfield <bruce.ashfield@gmail.com>
Richard,
Here's the next set of -stable updates to the active kernels, a -rt
bugfix import and some configuration tweaks requested by Ross.
I do have commits locally to make 5.13 the default kernel for the
reference poky layers, but I'm heading out on vacation and won't
be around to do a lot of debugging if they cause issues.
I was planning on holding them and sending them, plus the 5.4 removal
in mid August. If you want them sooner, or for testing, I can make
them available .. just let me know.
Bruce
The following changes since commit 4a1381d350aa1acc75ca1e6d03b8067483c162f5:
archiver.bbclass: fix do_ar_configured failure for kernel (2021-07-28 23:47:00 +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.10: update to v5.10.53
linux-yocto/5.13: update to v5.13.5
linux-yocto/5.4: update to v5.4.135
linux-yocto-rt/5.10: update to -rt47
linux-yocto/5.10: enable TYPEC_TCPCI in usbc fragment
linux-yocto/5.13: enable TYPEC_TCPCI in usbc fragment
.../linux/linux-yocto-rt_5.10.bb | 6 ++---
.../linux/linux-yocto-rt_5.13.bb | 6 ++---
.../linux/linux-yocto-rt_5.4.bb | 6 ++---
.../linux/linux-yocto-tiny_5.10.bb | 8 +++---
.../linux/linux-yocto-tiny_5.13.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.13.bb | 26 +++++++++----------
meta/recipes-kernel/linux/linux-yocto_5.4.bb | 22 ++++++++--------
9 files changed, 57 insertions(+), 57 deletions(-)
--
2.19.1
next reply other threads:[~2021-07-29 4:50 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-29 4:49 Bruce Ashfield [this message]
2021-07-29 4:49 ` [PATCH 1/6] linux-yocto/5.10: update to v5.10.53 Bruce Ashfield
2021-07-29 4:49 ` [PATCH 2/6] linux-yocto/5.13: update to v5.13.5 Bruce Ashfield
2021-07-29 4:50 ` [PATCH 3/6] linux-yocto/5.4: update to v5.4.135 Bruce Ashfield
2021-07-29 4:50 ` [PATCH 4/6] linux-yocto-rt/5.10: update to -rt47 Bruce Ashfield
2021-07-29 4:50 ` [PATCH 5/6] linux-yocto/5.10: enable TYPEC_TCPCI in usbc fragment Bruce Ashfield
2021-07-29 4:50 ` [PATCH 6/6] linux-yocto/5.13: " 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-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.1627533955.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