Openembedded Core Discussions
 help / color / mirror / Atom feed
From: bruce.ashfield@gmail.com
To: richard.purdie@linuxfoundation.org
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/4] kernel-yocto: -stable and reproduciblity fixes
Date: Sun, 10 Jul 2022 22:25:40 -0400	[thread overview]
Message-ID: <cover.1657506122.git.bruce.ashfield@gmail.com> (raw)

From: Bruce Ashfield <bruce.ashfield@gmail.com>

Richard,

Here's the next set of updates to -stable (I had already staged
them before we ran into the buildpaths QA issues), and on top of
them is a RFC fix that I did for the buildpaths issue you found
in the linux-src package with the conmakehash.

That fix is still preliminary, as i haven't triggered the error
here, but I did inspect the output of my build and can confirm the
full path is gone. It isn't appropriate for upstream yet, and only
fixes the issues for 5.15 linux-yocto, but we can expand it to
other linux-yocto versions later.

Also, ther's another fix to devsrc for ppc32 to remove the vdso
file causing the build paths warning.

Bruce

The following changes since commit dc184d6aaf282f28fe96cce2f01bf20f09821645:

  gperf: Switch to upstream patch (2022-07-09 20:58:35 +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 (4):
  linux-yocto/5.15: update to v5.15.52
  linux-yocto/5.10: update to v5.10.128
  kernel-devsrc: ppc32: fix reproducibility
  linux-yocto/5.15: fix qemuppc buildpaths warning

 meta/recipes-kernel/linux/kernel-devsrc.bb    |  4 ++-
 .../linux/linux-yocto-rt_5.10.bb              |  6 ++und---
 .../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 +++++++++----------
 7 files changed, 41 insertions(+), 39 deletions(-)

-- 
2.19.1



             reply	other threads:[~2022-07-11  2:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-11  2:25 bruce.ashfield [this message]
2022-07-11  2:25 ` [PATCH 1/4] linux-yocto/5.15: update to v5.15.52 bruce.ashfield
2022-07-11  2:25 ` [PATCH 2/4] linux-yocto/5.10: update to v5.10.128 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.1657506122.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