From: "Yoann Congal" <yoann.congal@smile.fr>
To: "Yoann Congal" <yoann.congal@smile.fr>,
<bruce.ashfield@gmail.com>, <richard.purdie@linuxfoundation.org>
Cc: <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH 0/5] linux-yocto: -stable updates
Date: Tue, 08 Sep 2026 11:26:00 +0200 [thread overview]
Message-ID: <DL9TSH9C0F4T.4GBXSMFY7MTZ@smile.fr> (raw)
In-Reply-To: <DL9SAQQDYUWN.DHAPJINZ988O@smile.fr>
On Tue Sep 8, 2026 at 10:15 AM CEST, Yoann Congal wrote:
> On Tue Sep 8, 2026 at 3:17 AM CEST, Bruce Ashfield via lists.openembedded.org wrote:
>> From: Bruce Ashfield <bruce.ashfield@gmail.com>
>>
>> Hi all,
>>
>> Since we are working through 7.2 integration, I wanted to get these
>> stable updates out while the older (6.18 and less) are still under
>> test (those -stable updates will follow).
>>
>> I did sneak a 6.18-rt update in, but it was trivial and tested
>> independently.
>>
>> (yes, the yocto-bsps update is in this series, even though it
>> is for the yocto-bsp repo)
>>
>> Cheers,
>>
>> Bruce
>>
>>
>> openembedded-core (4):
>> linux-yocto/7.2: menuconfig,mconf-cfg: Fix broken menuconfig
>> linux-yocto/7.2: rt: update to v7.2-rt5
>> linux-yocto/6.18: rt: update to v6.18.37-rt6
>> linux-yocto/7.2: update to v7.2.4
>>
>> meta-yocto (1):
>> yocto-bsps: update to v7.2.4
>>
>> openembedded-core:
>> meta/recipes-kernel/linux/linux-yocto-rt_6.18.bb | 4 ++--
>> meta/recipes-kernel/linux/linux-yocto-rt_7.2.bb | 6 +++---
>> meta/recipes-kernel/linux/linux-yocto-tiny_6.18.bb | 4 ++--
>> meta/recipes-kernel/linux/linux-yocto-tiny_7.2.bb | 6 +++---
>> meta/recipes-kernel/linux/linux-yocto_6.18.bb | 20 ++++++++++----------
>> meta/recipes-kernel/linux/linux-yocto_7.2.bb | 24 ++++++++++++------------
>> 6 files changed, 32 insertions(+), 32 deletions(-)
>>
>> meta-yocto:
>> meta-yocto-bsp/recipes-kernel/linux/linux-yocto_7.2.bbappend | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> Hello,
>
> Is there a chance that a fix for #16414 "AB-INT: testsdk:
> kernel-module-hello-world build fail"[0] hides somewhere in this
> upgrade?
>
> [0]: https://bugzilla.yoctoproject.org/show_bug.cgi?id=16414
>
> Thanks!
Answering myself:
Richard just updated the bug, the fix is: "kernel-module-split: Remove get_ext_mod"
https://git.openembedded.org/openembedded-core/commit/?id=02890c1eff104de94ad22023232fd36baaf228dc
Thanks!
--
Yoann Congal
Smile ECS
prev parent reply other threads:[~2026-09-08 9:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-08 1:17 [PATCH 0/5] linux-yocto: -stable updates bruce.ashfield
2026-09-08 1:17 ` [meta][PATCH 01/05] linux-yocto/7.2: menuconfig,mconf-cfg: Fix broken menuconfig outside of Yocto env bruce.ashfield
2026-09-08 1:17 ` [meta][PATCH 02/05] linux-yocto/7.2: rt: update to v7.2-rt5 bruce.ashfield
2026-09-08 1:17 ` [meta][PATCH 03/05] linux-yocto/6.18: rt: update to v6.18.37-rt6 bruce.ashfield
2026-09-08 1:17 ` [meta][PATCH 04/05] linux-yocto/7.2: update to v7.2.4 bruce.ashfield
2026-09-08 1:17 ` [meta-yocto-bsp][PATCH 05/05] yocto-bsps: " bruce.ashfield
2026-09-08 1:32 ` Patchtest results for " patchtest
2026-09-08 8:15 ` [OE-core] [PATCH 0/5] linux-yocto: -stable updates Yoann Congal
2026-09-08 9:22 ` Richard Purdie
2026-09-08 9:26 ` Yoann Congal [this message]
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=DL9TSH9C0F4T.4GBXSMFY7MTZ@smile.fr \
--to=yoann.congal@smile.fr \
--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