Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <bruce.ashfield@gmail.com>, <richard.purdie@linuxfoundation.org>
Cc: <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH 0/4] kernel-yocto: -stable and new reference kernel
Date: Fri, 22 Aug 2025 17:52:00 +0200	[thread overview]
Message-ID: <DC92RWVBN7V4.30RLT0SCEWDPC@bootlin.com> (raw)
In-Reply-To: <cover.1755784780.git.bruce.ashfield@gmail.com>

On Thu Aug 21, 2025 at 4:03 PM CEST, Bruce Ashfield via lists.openembedded.org wrote:
> From: Bruce Ashfield <bruce.ashfield@gmail.com>
>
> Richard,
>
> Here's the next set of updates to the linux-yocto kernel.
>
> The plan is to introduce 6.16 as the latest reference kernel, and keep
> 6.12 around (since it is a LTS).
>
> This isn't ready to be the default for builds, but it has passed my
> core-iamge-kernel-dev testing, so I wanted to make the recipes available
> as visibility to where we are headed for the release (plus, I'm out of
> the office on holidays until the first week of September, so making it
> the default would be a bad idea from me being able to support issues).
>

Hi Bruce,

Thanks for the series.

I understand this isn't fully ready, but I did launch a full build
anyway: most builders succeed, we just have one warning on config
fragments:

WARNING: linux-yocto-6.16.2+git-r0 do_kernel_configcheck: [kernel config]: specified values did not make it into the kernel's final configuration:
...
[INFO]: config 'CONFIG_CRYPTO_LIB_CHACHA' was set, but it wasn't assignable, check (parent) dependencies
...
[INFO]: config 'CONFIG_CRYPTO_CHACHA20_NEON' was set, but it wasn't assignable, check (parent) dependencies
...
[INFO]: the following symbols were not found in the active configuration:
     - CONFIG_CRYPTO_SHA2_ARM_CE
     - CONFIG_CRYPTO_CRC32_ARM_CE

https://autobuilder.yoctoproject.org/valkyrie/#/builders/40/builds/2248

Best regards,
Mathieu

-- 
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com



  parent reply	other threads:[~2025-08-22 15:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-21 14:03 [PATCH 0/4] kernel-yocto: -stable and new reference kernel bruce.ashfield
2025-08-21 14:03 ` [PATCH 1/4] linux-yocto: introduce 6.16 reference kernels bruce.ashfield
2025-08-21 14:03 ` [PATCH 2/4] linux-yocto/6.16: update CVE exclusions (6.16.2) bruce.ashfield
2025-08-21 14:03 ` [PATCH 3/4] linux-yocto/6.12: update to v6.12.42 bruce.ashfield
2025-08-21 14:03 ` [PATCH 4/4] linux-yocto/6.12: update CVE exclusions (6.12.42) bruce.ashfield
2025-08-22 15:52 ` Mathieu Dubois-Briand [this message]
2025-08-26  2:03   ` [OE-core] [PATCH 0/4] kernel-yocto: -stable and new reference kernel Bruce Ashfield
2025-08-26  6:57     ` Mathieu Dubois-Briand
2025-08-26  7:15     ` Richard Purdie
2025-08-26 13:57       ` 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=DC92RWVBN7V4.30RLT0SCEWDPC@bootlin.com \
    --to=mathieu.dubois-briand@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