From: bruce.ashfield@gmail.com
To: richard.purdie@linuxfoundation.org
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH 00/10] linux-yocto: consolidated pull request
Date: Thu, 14 Jul 2022 15:14:43 -0400 [thread overview]
Message-ID: <cover.1657825809.git.bruce.ashfield@gmail.com> (raw)
From: Bruce Ashfield <bruce.ashfield@gmail.com>
Richard,
The gen-mach-types patches are repeats of ones I sent before, but I've
included them to make the ordering clear.
After that, we have two -stable updates (getting ready for the "big"
CVE updates)
And then the pnmtologo fixes. That should be all the builpaths warnings.
I'm sending this all to oe-core fo simplicty sake, but obviously the
yocto-bsp ones are for the yocto layers.
Brue
The following changes since commit e65ee81d621e679107b5f4ef2dbbb8d1786e93ad:
ltp: fix builds when host ld doesn't know about target ELF formats (2022-07-14 10:08:57 +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 (10):
linux-yocto/5.10: fix buildpaths issue with gen-mach-types
linux-yocto/5.15: fix buildpaths issue with gen-mach-types
yocto-bsps/5.10: fix buildpaths issue with gen-mach-types
yocto-bsps/5.15: fix buildpaths issue with gen-mach-types
linux-yocto/5.15: update to v5.15.54
linux-yocto/5.10: update to v5.10.130
linux-yocto/5.15: fix buildpaths issue with pnmtologo
linux-yocto/5.10: fix buildpaths issue with pnmtologo
yocto-bsps/5.10: fix buildpaths issue with pnmtologo
yocto-bsps/5.15: fix buildpaths issue with pnmtologo
.../linux/linux-yocto_5.10.bbappend | 8 +++---
.../linux/linux-yocto_5.15.bbappend | 8 +++---
.../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 | 6 ++---
meta/recipes-kernel/linux/linux-yocto_5.10.bb | 24 ++++++++---------
meta/recipes-kernel/linux/linux-yocto_5.15.bb | 26 +++++++++----------
8 files changed, 46 insertions(+), 46 deletions(-)
--
2.19.1
next reply other threads:[~2022-07-14 19:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-14 19:14 bruce.ashfield [this message]
2022-07-14 19:14 ` [PATCH 01/10] linux-yocto/5.10: fix buildpaths issue with gen-mach-types bruce.ashfield
2022-07-14 19:14 ` [PATCH 02/10] linux-yocto/5.15: " bruce.ashfield
2022-07-14 19:14 ` [PATCH 03/10] yocto-bsps/5.10: " bruce.ashfield
2022-07-14 19:14 ` [PATCH 04/10] yocto-bsps/5.15: " bruce.ashfield
2022-07-14 19:14 ` [PATCH 05/10] linux-yocto/5.15: update to v5.15.54 bruce.ashfield
2022-07-14 19:14 ` [PATCH 06/10] linux-yocto/5.10: update to v5.10.130 bruce.ashfield
2022-07-14 19:14 ` [PATCH 07/10] linux-yocto/5.15: fix buildpaths issue with pnmtologo bruce.ashfield
2022-07-14 19:14 ` [PATCH 08/10] linux-yocto/5.10: " bruce.ashfield
2022-07-14 19:14 ` [PATCH 09/10] yocto-bsps/5.10: " bruce.ashfield
2022-07-14 19:14 ` [PATCH 10/10] yocto-bsps/5.15: " bruce.ashfield
-- strict thread matches above, loose matches on Subject: below --
2023-08-21 15:44 [PATCH 00/10] linux-yocto: consolidated pull request bruce.ashfield
2023-08-21 15:47 ` Richard Purdie
2023-08-21 15:50 ` 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.1657825809.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