From: "Bruce Ashfield" <bruce.ashfield@gmail.com>
To: richard.purdie@linuxfoundation.org
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/3] kernel-yocto: -stable bumps and config cleanup
Date: Wed, 26 Aug 2020 09:57:28 -0400 [thread overview]
Message-ID: <cover.1598450136.git.bruce.ashfield@gmail.com> (raw)
From: Bruce Ashfield <bruce.ashfield@gmail.com>
Richard,
Here's the next set of -stable bumps and the collected configuration cleanups
over the past few days.
With these, we have no warnings on the newly uprev'd yocto-bsps.
Note: that the yocto-bsps configs are stacked on top of my already queued
-stable update. So on the off chance we have issues with those stable updates,
we'll have to jiggle the SRCREVs a bit to just take the config cleanups.
Bruce
The following changes since commit 2b3bd34f9b1f6db9651918532ff5a68de13a93b4:
bitbake: server/process: Fix typo in code causing tracebacks (2020-08-26 11:28:54 +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 (3):
linux-yocto/5.8: update to v5.8.3
linux-yocto/5.4: update to v5.4.60
kernel: config cleanups for 5.8+
.../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 +++++++++----------
6 files changed, 36 insertions(+), 36 deletions(-)
--
2.19.1
next reply other threads:[~2020-08-26 13:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-26 13:57 Bruce Ashfield [this message]
2020-08-26 13:57 ` [PATCH 1/3] linux-yocto/5.8: update to v5.8.3 Bruce Ashfield
2020-08-26 13:57 ` [PATCH 2/3] linux-yocto/5.4: update to v5.4.60 Bruce Ashfield
2020-08-26 13:57 ` [PATCH 3/3] kernel: config cleanups for 5.8+ 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.1598450136.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.