Re: [OE-core] [PATCH 0/13] kernel-yocto: 6.18 updates and 6.12/6.16 removal

[Richard Purdie <richard.purdie@linuxfoundation.org>]

On Tue, 2026-02-10 at 09:15 -0500, Bruce Ashfield wrote:
> On Tue, Feb 10, 2026 at 8:19 AM Richard Purdie <richard.purdie@linuxfoundation.org> wrote:
> > It mostly worked in my testing except for:
> > 
> > https://autobuilder.yoctoproject.org/valkyrie/#/builders/60/builds/3148
> > https://autobuilder.yoctoproject.org/valkyrie/#/builders/22/builds/3176
> > 
> > linux-yocto-6.18.7+git-r0 do_kernel_version_sanity_check: Package Version (6.18.7+git) does not match of kernel being built (6.18.8). Please update the PV variable to match the kernel source or set KERNEL_VERSION_SANITY_SKIP="1" in your recipe.
> > 
> > Did I miss a patch or something?
> > 
> 
> 
> I also just sent another patch to the bbappend, to bump it to 6.18.9, but you
> can ignore that patch, as I haven't sent the base uprev yet.
> 
> genericarm64 has its own SRCREV, so we always need the patch to bump
> it along with the base kernel or we'll get those version mismatch warnings.
> 
> I could fix it by putting a PV into the bbappend, and then only when I update
> both the SRCREV and the PV will the reference board move forward .. but
> I think we should leave it as-is, since it prevents them from falling behind
> the other qemu based reference boards.

Mathieu is right, I had missed two patches. What happened is groups.io
sent some to me directly and some to the oe-core list. This meant my
mail filtering did something different with the patches and I didn't
spot it.

Normally the numbering would give me a clue but I'd already had issues
applying things as there were conflicts with something else in master-
next I removed.

So sorry about that, my fault and I at least know how it went wrong and
how to avoid it, sorry about the noise!

Cheers,

Richard