From: bruce.ashfield@gmail.com
To: richard.purdie@linuxfoundation.org
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH 2/2] linux-yocto-dev: enable BSP config audit reporting
Date: Tue, 21 Jul 2026 23:51:39 -0400 [thread overview]
Message-ID: <20260722035139.1349872-2-bruce.ashfield@gmail.com> (raw)
In-Reply-To: <20260722035139.1349872-1-bruce.ashfield@gmail.com>
From: Bruce Ashfield <bruce.ashfield@gmail.com>
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.
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
---
meta/recipes-kernel/linux/linux-yocto-dev.bb | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/recipes-kernel/linux/linux-yocto-dev.bb b/meta/recipes-kernel/linux/linux-yocto-dev.bb
index f82f3c326b..ef6e1e0759 100644
--- a/meta/recipes-kernel/linux/linux-yocto-dev.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-dev.bb
@@ -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"
--
2.43.0
next prev parent reply other threads:[~2026-07-22 3:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-22 3:51 [PATCH 1/2] linux-yocto-dev: bump to v7.2 bruce.ashfield
2026-07-22 3:51 ` bruce.ashfield [this message]
2026-07-22 6:49 ` [PATCH 2/2] linux-yocto-dev: enable BSP config audit reporting Richard Purdie
2026-07-22 12:47 ` 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=20260722035139.1349872-2-bruce.ashfield@gmail.com \
--to=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