From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>,
bruce.ashfield@gmail.com
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 0/6] kernel-yocto: consolidated pull request
Date: Wed, 07 May 2025 08:58:58 +0100 [thread overview]
Message-ID: <f108401a73fca43946481dd2488fbb05cd8540d8.camel@linuxfoundation.org> (raw)
In-Reply-To: <D9PRCP2WLN68.1VIO3IX3SQ7IH@bootlin.com>
On Wed, 2025-05-07 at 09:42 +0200, Mathieu Dubois-Briand wrote:
> On Tue May 6, 2025 at 6:32 PM CEST, Bruce Ashfield via lists.openembedded.org wrote:
> > From: Bruce Ashfield <bruce.ashfield@gmail.com>
> >
> > Hi Richard,
> >
> > Now that I'm back at my desk, here are the queued -stable, configuration
> > and feature changes that I have queued.
> >
> > I'll be sending -stable updates to the LTS branches as well.
> >
> > Note: once patch #1 is in the tree and doesn't need any more tweaks, I'll
> > send a documenation update. This is the patch that we need to enable the
> > modular initrd work in kernel-yocto references.
>
> I took this series in my branch and everything seems to be fine so far,
> except for a warning:
>
> WARNING: linux-yocto-tiny-6.12.27+git-r0 do_kernel_configcheck: [kernel config]: specified values did not make it into the kernel's final configuration:
>
> [NOTE]: 'CONFIG_CRYPTO_CHACHA20_NEON' last val (y) and .config val (n) do not match
> [INFO]: CONFIG_CRYPTO_CHACHA20_NEON : n
>
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/50/builds/1565
There are a few, it likely depends which build built a component first.
I think there are three groups of failures, I've listed them all for
completeness:
Another qemuarm poky-tiny:
https://autobuilder.yoctoproject.org/valkyrie/?#/builders/50/builds/1564
qemuarm:
https://autobuilder.yoctoproject.org/valkyrie/?#/builders/16/builds/1563
qemuarm-alt:
https://autobuilder.yoctoproject.org/valkyrie/?#/builders/74/builds/1532
qemuarm nodistro:
https://autobuilder.yoctoproject.org/valkyrie/?#/builders/40/builds/1531
lttng-tools ptest failure:
https://autobuilder.yoctoproject.org/valkyrie/?#/builders/61/builds/1445
genericarm64:
https://autobuilder.yoctoproject.org/valkyrie/?#/builders/60/builds/1549
genericarm64-alt:
https://autobuilder.yoctoproject.org/valkyrie/?#/builders/22/builds/1552
Cheers,
Richard
next prev parent reply other threads:[~2025-05-07 7:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-06 16:32 [PATCH 0/6] kernel-yocto: consolidated pull request bruce.ashfield
2025-05-06 16:32 ` [PATCH 1/6] kernel-yocto: allow annotated options to be modified bruce.ashfield
2025-05-06 16:32 ` [PATCH 2/6] linux-yocto-dev: update to v6.15 bruce.ashfield
2025-05-06 16:32 ` [PATCH 3/6] linux-yocto/6.12: update to v6.12.24 bruce.ashfield
2025-05-06 16:32 ` [PATCH 4/6] linux-yocto/6.12: update to v6.12.25 bruce.ashfield
2025-05-06 16:32 ` [PATCH 5/6] linux-yocto/6.12: bsp/genericarm64: modular configuration updates bruce.ashfield
2025-05-06 16:33 ` [PATCH 6/6] linux-yocto/6.12: update to v6.12.27 bruce.ashfield
2025-05-07 7:42 ` [OE-core] [PATCH 0/6] kernel-yocto: consolidated pull request Mathieu Dubois-Briand
2025-05-07 7:58 ` Richard Purdie [this message]
[not found] ` <183D2FC291E34522.16348@lists.openembedded.org>
2025-05-07 11:18 ` Richard Purdie
2025-05-07 11:39 ` Mikko Rapeli
2025-05-07 13:03 ` Bruce Ashfield
2025-05-15 16:06 ` Fabio Estevam
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=f108401a73fca43946481dd2488fbb05cd8540d8.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=bruce.ashfield@gmail.com \
--cc=mathieu.dubois-briand@bootlin.com \
--cc=openembedded-core@lists.openembedded.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