Skip to contentSkip to conversation

linux-yocto-dev: bump to v7.2

PATCH In review [email protected] 2 participants 4 messages Jul 22

lore
Share & tools
lore
#0 lore raw

PATCH 1/2 linux-yocto-dev: bump to v7.2

From: Bruce Ashfield <[email protected]>

Track the newly generated v7.2 branches in linux-yocto-dev, built on v7.2-rc4.

---
 meta/recipes-kernel/linux/linux-yocto-dev.bb | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
meta/recipes-kernel/linux/linux-yocto-dev.bb +2 -2
index 883b4e3151..f82f3c326b 100644
@@ -14,7 +14,7 @@ require recipes-kernel/linux/linux-yocto.inc
 # provide this .inc to set specific revisions
 include recipes-kernel/linux/linux-yocto-dev-revisions.inc
 
-KBRANCH = "v7.1/standard/base"
+KBRANCH = "v7.2/standard/base"
 KMETA = "kernel-meta"
 
 SRC_URI = "git://git.yoctoproject.org/linux-yocto-dev.git;branch=${KBRANCH};name=machine;protocol=https \
@@ -28,7 +28,7 @@ SRC_URI = "git://git.yoctoproject.org/linux-yocto-dev.git;branch=${KBRANCH};name
 SRCREV_machine ?= '${@oe.utils.conditional("PREFERRED_PROVIDER_virtual/kernel", "linux-yocto-dev", "${AUTOREV}", "29594404d7fe73cd80eaa4ee8c43dcc53970c60e", d)}'
 SRCREV_meta ?= '${@oe.utils.conditional("PREFERRED_PROVIDER_virtual/kernel", "linux-yocto-dev", "${AUTOREV}", "29594404d7fe73cd80eaa4ee8c43dcc53970c60e", d)}'
 
-LINUX_VERSION ?= "7.1"
+LINUX_VERSION ?= "7.2"
 LINUX_VERSION_EXTENSION ?= "-yoctodev-${LINUX_KERNEL_TYPE}"
 PV = "${LINUX_VERSION}+git"
 
Signature · 1 line
2.43.0
#1 lore raw

PATCH 2/2 linux-yocto-dev: enable BSP config audit reporting

From: Bruce Ashfield <[email protected]>

linux-yocto-dev did not set KCONF_BSP_AUDIT_LEVEL, so it inherited the kernel-yocto.bbclass default of 0. That silently suppresses the 'invalid fragment elements' and 'redefinition' audit categories: do_kernel_configcheck still runs and still writes .kernel-meta/cfg/{invalid,redefinition}.txt, but nothing is ever reported to the user.

This was hiding real breakage. Five config options removed upstream in v7.1 (CONFIG_HAMRADIO, CONFIG_CRYPTO_MICHAEL_MIC, CONFIG_ISDN, CONFIG_ISDN_CAPI, CONFIG_NF_CT_PROTO_UDPLITE) sat stale in the kernel-cache fragments for a full release cycle without a single warning.

The versioned recipes already set this (linux-yocto and linux-yocto-rt use 1, linux-yocto-tiny uses 2); the dev recipe being the sole exception is backwards, since the dev kernel tracks a moving upstream and is precisely where dropped symbols should surface first.

Set it to 1 to match linux-yocto.

---
 meta/recipes-kernel/linux/linux-yocto-dev.bb | 1 +
 1 file changed, 1 insertion(+)
meta/recipes-kernel/linux/linux-yocto-dev.bb +1 -0
index f82f3c326b..ef6e1e0759 100644
@@ -16,6 +16,7 @@ include recipes-kernel/linux/linux-yocto-dev-revisions.inc
 
 KBRANCH = "v7.2/standard/base"
 KMETA = "kernel-meta"
+KCONF_BSP_AUDIT_LEVEL = "1"
 
 SRC_URI = "git://git.yoctoproject.org/linux-yocto-dev.git;branch=${KBRANCH};name=machine;protocol=https \
            git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=master;destsuffix=${KMETA};protocol=https"
Signature · 1 line
2.43.0
#2 lore raw

Re: [PATCH 2/2] linux-yocto-dev: enable BSP config audit reporting

Quoted 30 lines · On Tue, 2026-07-21 at 23:51 -0400, [email protected] wrote:

From: Bruce Ashfield <[email protected]>

linux-yocto-dev did not set KCONF_BSP_AUDIT_LEVEL, so it inherited the kernel-yocto.bbclass default of 0. That silently suppresses the 'invalid fragment elements' and 'redefinition' audit categories: do_kernel_configcheck still runs and still writes .kernel-meta/cfg/{invalid,redefinition}.txt, but nothing is ever reported to the user.

This was hiding real breakage. Five config options removed upstream in v7.1 (CONFIG_HAMRADIO, CONFIG_CRYPTO_MICHAEL_MIC, CONFIG_ISDN, CONFIG_ISDN_CAPI, CONFIG_NF_CT_PROTO_UDPLITE) sat stale in the kernel-cache fragments for a full release cycle without a single warning.

The versioned recipes already set this (linux-yocto and linux-yocto-rt use 1, linux-yocto-tiny uses 2); the dev recipe being the sole exception is backwards, since the dev kernel tracks a moving upstream and is precisely where dropped symbols should surface first.

Set it to 1 to match linux-yocto.

---
 meta/recipes-kernel/linux/linux-yocto-dev.bb | 1 +

 1 file changed, 1 insertion(+)
meta/recipes-kernel/linux/linux-yocto-dev.bb +0 -0
index f82f3c326b..ef6e1e0759 100644
@@ -16,6 +16,7 @@ include recipes-kernel/linux/linux-yocto-dev-revisions.inc
Quoted 4 lines


 KBRANCH = "v7.2/standard/base"
 KMETA = "kernel-meta"
+KCONF_BSP_AUDIT_LEVEL = "1"

Should we change the default now this is well established?

Cheers,

Richard

#3 lore raw

Re: [PATCH 2/2] linux-yocto-dev: enable BSP config audit reporting

Quoted 33 lines · Richard Purdie
Quoted 31 lines · On Tue, 2026-07-21 at 23:51 -0400, [email protected] wrote:

From: Bruce Ashfield <[email protected]>

linux-yocto-dev did not set KCONF_BSP_AUDIT_LEVEL, so it inherited the kernel-yocto.bbclass default of 0. That silently suppresses the 'invalid fragment elements' and 'redefinition' audit categories: do_kernel_configcheck still runs and still writes .kernel-meta/cfg/{invalid,redefinition}.txt, but nothing is ever reported to the user.

This was hiding real breakage. Five config options removed upstream in v7.1 (CONFIG_HAMRADIO, CONFIG_CRYPTO_MICHAEL_MIC, CONFIG_ISDN, CONFIG_ISDN_CAPI, CONFIG_NF_CT_PROTO_UDPLITE) sat stale in the kernel-cache fragments for a full release cycle without a single warning.

The versioned recipes already set this (linux-yocto and linux-yocto-rt use 1, linux-yocto-tiny uses 2); the dev recipe being the sole exception is backwards, since the dev kernel tracks a moving upstream and is precisely where dropped symbols should surface first.

Set it to 1 to match linux-yocto.

---
 meta/recipes-kernel/linux/linux-yocto-dev.bb | 1 +
 1 file changed, 1 insertion(+)
meta/recipes-kernel/linux/linux-yocto-dev.bb +0 -0
index f82f3c326b..ef6e1e0759 100644
@@ -16,6 +16,7 @@ include recipes-kernel/linux/linux-yocto-dev-revisions.inc
 
Quoted 7 lines

meta/recipes-kernel/linux/linux-yocto-dev.bb include recipes-kernel/linux/linux-yocto-dev-revisions.inc · line 19

Quoted 3 lines
meta/recipes-kernel/linux/linux-yocto-dev.bb +1 -0
 KBRANCH = "v7.2/standard/base"
 KMETA = "kernel-meta"
+KCONF_BSP_AUDIT_LEVEL = "1"

Should we change the default now this is well established?

I get enough complaints about the fragments and folks needing to inherit kernel-yocto, etc, so I'd prefer to just keep the audit off and let them opt-in so the default behaviour is as close to a "regular" kernel build as possible.

Bruce

Quoted 4 lines

Cheers,

Richard

Signature · 3 lines
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II