From: "Bruce Ashfield" <bruce.ashfield@gmail.com>
To: richard.purdie@linuxfoundation.org
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH 00/11] linux-yocto: consolidated pull request
Date: Tue, 17 Nov 2020 10:24:26 -0500 [thread overview]
Message-ID: <cover.1605626488.git.bruce.ashfield@gmail.com> (raw)
From: Bruce Ashfield <bruce.ashfield@gmail.com>
Richard,
I had sent some of these before, but on my latest rebase I see they are
still outstanding.
Feel free to drop ones that you already have queued, since I've included
all my tested -stable updates. I've also kept 5.4 separate from 5.8 in
config chanages, so Steve can pick them up more easily.
I'm doing another round of -stable updates now, so I wanted to send these
again first.
Cheers,
Bruce
The following changes since commit eced9bcb337087c076e847f8d9cbae95760c28ed:
kexec: arm64: disabled check if kaslr-seed dtb property was wiped (2020-11-16 14:27:46 +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 (11):
linux-yocto/5.8: update to v5.8.15
linux-yocto/5.4: update to v5.4.71
linux-yocto/5.8: update to v5.8.16
linux-yocto/5.4: update to v5.4.72
linux-yocto/5.8: update to v5.8.17
linux-yocto/5.4: update to v5.4.73
linux-yocto-dev: move to v5.10-rc
linux-yocto/5.4: config cleanup / warnings
linux-yocto/5.8: config cleanup / warnings
linux-yocto/5.8: update to v5.8.18
linux-yocto/5.4: update to v5.4.75
meta/recipes-kernel/linux/linux-yocto-dev.bb | 2 +-
.../linux/linux-yocto-rt_5.4.bb | 6 ++---
.../linux/linux-yocto-rt_5.8.bb | 6 ++---
.../linux/linux-yocto-tiny_5.4.bb | 8 +++----
.../linux/linux-yocto-tiny_5.8.bb | 8 +++----
meta/recipes-kernel/linux/linux-yocto_5.4.bb | 22 +++++++++----------
meta/recipes-kernel/linux/linux-yocto_5.8.bb | 22 +++++++++----------
7 files changed, 37 insertions(+), 37 deletions(-)
--
2.19.1
next reply other threads:[~2020-11-17 15:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-17 15:24 Bruce Ashfield [this message]
2020-11-17 15:24 ` [PATCH 01/11] linux-yocto/5.8: update to v5.8.15 Bruce Ashfield
2020-11-17 15:24 ` [PATCH 02/11] linux-yocto/5.4: update to v5.4.71 Bruce Ashfield
2020-11-17 15:24 ` [PATCH 03/11] linux-yocto/5.8: update to v5.8.16 Bruce Ashfield
2020-11-17 15:24 ` [PATCH 04/11] linux-yocto/5.4: update to v5.4.72 Bruce Ashfield
2020-11-17 15:24 ` [PATCH 05/11] linux-yocto/5.8: update to v5.8.17 Bruce Ashfield
2020-11-17 15:24 ` [PATCH 06/11] linux-yocto/5.4: update to v5.4.73 Bruce Ashfield
2020-11-17 15:24 ` [PATCH 07/11] linux-yocto-dev: move to v5.10-rc Bruce Ashfield
2020-11-17 15:24 ` [PATCH 08/11] linux-yocto/5.4: config cleanup / warnings Bruce Ashfield
2020-11-17 15:24 ` [PATCH 09/11] linux-yocto/5.8: " Bruce Ashfield
2020-11-17 15:24 ` [PATCH 10/11] linux-yocto/5.8: update to v5.8.18 Bruce Ashfield
2020-11-17 15:24 ` [PATCH 11/11] linux-yocto/5.4: update to v5.4.75 Bruce Ashfield
-- strict thread matches above, loose matches on Subject: below --
2024-01-19 21:14 [PATCH 00/11] linux-yocto: consolidated pull request 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.1605626488.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