Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: richard.purdie@linuxfoundation.org,
	openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 0/9] kernel: consolidated pull request
Date: Wed, 21 Dec 2022 16:58:09 +0100	[thread overview]
Message-ID: <Y6MtEWtI2N7AAlK0@mail.local> (raw)
In-Reply-To: <cover.1671560768.git.bruce.ashfield@gmail.com>

Hello Bruce,

I think I applied everything properly and I end up with the following
error for multiple architectures:

stdio: ERROR: linux-yocto-5.15.78+gitAUTOINC+72756ee16d_24c30a8e9f-r0 do_kernel_version_sanity_check: Package Version (5.15.78+gitAUTOINC+72756ee16d_24c30a8e9f) does not match of kernel being built (5.15.84). Please update the PV variable to match the kernel source or set KERNEL_VERSION_SANITY_SKIP="1" in your recipe.
stdio: ERROR: linux-yocto-5.15.78+gitAUTOINC+72756ee16d_24c30a8e9f-r0 do_kernel_version_sanity_check: ExecutionError('/home/pokybuild/yocto-worker/qemuarm-alt/build/build/tmp/work/qemuarm-poky-linux-gnueabi/linux-yocto/5.15.78+gitAUTOINC+72756ee16d_24c30a8e9f-r0/temp/run.do_kernel_version_sanity_check.3360864', 1, None, None)

https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/5262/steps/11/logs/errors
https://autobuilder.yoctoproject.org/typhoon/#builders/131/builds/1756/steps/12/logs/errors
https://autobuilder.yoctoproject.org/typhoon/#builders/102/builds/3982/steps/12/logs/errors
https://autobuilder.yoctoproject.org/typhoon/#builders/107/builds/3957/steps/11/logs/errors
https://autobuilder.yoctoproject.org/typhoon/#builders/109/builds/5225/steps/11/logs/errors
https://autobuilder.yoctoproject.org/typhoon/#builders/101/builds/5156/steps/11/logs/errors


On 20/12/2022 13:42:01-0500, Bruce Ashfield wrote:
> From: Bruce Ashfield <bruce.ashfield@gmail.com>
> 
> Richard,
> 
> Most of these are -stable udpates, mixed in are a couple of clang fixes
> from Khem, and of course the bigger items of the libc-headers bump and
> the v6.1 reference kernel recipes.
> 
> I've built both musl and glibc for all architectures with the new libc
> headers, and sent patches last week for issues that I found in core or
> meta-oe.
> 
> That being said, I'm sure there's something .. somewhere lurking, but
> there's no sense sitting on it longer.
> 
> As for the 6.1 reference kernel, I've done the same. Built and booted
> core-image-minimal, sato and kernel dev on all architectures. The changes
> sent before the last release meant that our normal culprits of lttng-modules
> and kernel-devsrc don't need any tweaking to work. -rt has also been
> tested.
> 
> We can't make 6.1 the default yet, as the reference h/w BSPs need to
> be updated, and then 5.19 removed. But again, no sense sitting on these
> longer.
> 
> I'm around full time for the rest of this week, and then off and on
> through the first week of January to squash any fallout from the
> updates.
> 
> Cheers,
> 
> Bruce
> 
> The following changes since commit ace02cec70a4a1bc9088044905b3c4a801a39a1b:
> 
>   systemd: Make importd depend on glib-2.0 again (2022-12-18 19:48:00 +0000)
> 
> are available in the Git repository at:
> 
>   https://git.yoctoproject.org/poky-contrib zedd/kernel
>   http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
> 
> Bruce Ashfield (9):
>   yocto-bsps/5.15: update to v5.15.78
>   linux-yocto/5.15: update to v5.15.80
>   linux-yocto/5.19: fix perf build with clang
>   linux-yocto/5.15: ltp and squashfs fixes
>   linux-libc-headers: bump to 6.1
>   linux-yocto: introduce v6.1 reference kernel recipes
>   linux-yocto/5.15: fix perf build with clang
>   linux-yocto/5.15: update to v5.15.84
>   linux-yocto/5.15: libbpf: Fix build warning on ref_ctr_off
> 
>  .../linux/linux-yocto_5.15.bbappend           | 16 ++---
>  meta/conf/distro/include/tcmode-default.inc   |  2 +-
>  ...d-input-and-output-files-instead-of-.patch | 67 ------------------
>  ...ders_5.19.bb => linux-libc-headers_6.1.bb} |  5 +-
>  .../linux/linux-yocto-rt_5.15.bb              |  4 +-
>  .../linux/linux-yocto-rt_5.19.bb              |  4 +-
>  .../linux/linux-yocto-rt_6.1.bb               | 45 ++++++++++++
>  .../linux/linux-yocto-tiny_5.15.bb            |  4 +-
>  .../linux/linux-yocto-tiny_5.19.bb            |  4 +-
>  .../linux/linux-yocto-tiny_6.1.bb             | 30 ++++++++
>  meta/recipes-kernel/linux/linux-yocto_5.15.bb | 24 +++----
>  meta/recipes-kernel/linux/linux-yocto_5.19.bb | 22 +++---
>  meta/recipes-kernel/linux/linux-yocto_6.1.bb  | 70 +++++++++++++++++++
>  13 files changed, 187 insertions(+), 110 deletions(-)
>  delete mode 100644 meta/recipes-kernel/linux-libc-headers/linux-libc-headers/0001-scripts-Use-fixed-input-and-output-files-instead-of-.patch
>  rename meta/recipes-kernel/linux-libc-headers/{linux-libc-headers_5.19.bb => linux-libc-headers_6.1.bb} (70%)
>  create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_6.1.bb
>  create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_6.1.bb
>  create mode 100644 meta/recipes-kernel/linux/linux-yocto_6.1.bb
> 
> -- 
> 2.37.3
> 

> 
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#174873): https://lists.openembedded.org/g/openembedded-core/message/174873
> Mute This Topic: https://lists.openembedded.org/mt/95791763/3617179
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [alexandre.belloni@bootlin.com]
> -=-=-=-=-=-=-=-=-=-=-=-
> 


-- 
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


  parent reply	other threads:[~2022-12-21 15:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-20 18:42 [PATCH 0/9] kernel: consolidated pull request bruce.ashfield
2022-12-20 18:42 ` [PATCH 1/9] yocto-bsps/5.15: update to v5.15.78 bruce.ashfield
2022-12-20 18:42 ` [PATCH 2/9] linux-yocto/5.15: update to v5.15.80 bruce.ashfield
2022-12-20 18:42 ` [PATCH 3/9] linux-yocto/5.19: fix perf build with clang bruce.ashfield
2022-12-20 18:42 ` [PATCH 4/9] linux-yocto/5.15: ltp and squashfs fixes bruce.ashfield
2022-12-20 18:42 ` [PATCH 5/9] linux-libc-headers: bump to 6.1 bruce.ashfield
2022-12-20 18:42 ` [PATCH 6/9] linux-yocto: introduce v6.1 reference kernel recipes bruce.ashfield
2022-12-20 18:42 ` [PATCH 7/9] linux-yocto/5.15: fix perf build with clang bruce.ashfield
2022-12-20 18:42 ` [PATCH 8/9] linux-yocto/5.15: update to v5.15.84 bruce.ashfield
2022-12-20 18:42 ` [PATCH 9/9] linux-yocto/5.15: libbpf: Fix build warning on ref_ctr_off bruce.ashfield
2022-12-21 15:58 ` Alexandre Belloni [this message]
2022-12-21 16:06   ` [OE-core] [PATCH 0/9] kernel: consolidated pull request Bruce Ashfield
2022-12-22 15:00 ` Alexandre Belloni
  -- strict thread matches above, loose matches on Subject: below --
2020-12-22 14:28 Bruce Ashfield
2020-12-23 12:32 ` Richard Purdie
2020-12-23 13:37   ` Bruce Ashfield
2020-12-23 23:03     ` Ross Burton
     [not found]       ` <16538A0D49119031.25471@lists.openembedded.org>
2020-12-24  3:43         ` [OE-core] " Bruce Ashfield
2020-12-24  8:14           ` Richard Purdie

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=Y6MtEWtI2N7AAlK0@mail.local \
    --to=alexandre.belloni@bootlin.com \
    --cc=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