Skip to contentSkip to conversation

linux-yocto/6.16: cfg fix configuration audit warnings

PATCH In review [email protected] 2 participants 3 messages Aug 27, 2025

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 linux-yocto/6.16: cfg fix configuration audit warnings

From: Bruce Ashfield <[email protected]>

Integrating the following commit(s) to linux-yocto/.:

1/1 [
Author: Bruce Ashfield
Email: [email protected]
Subject: arm/6.16: remove unsettable and obsolete options
Date: Tue, 26 Aug 2025 22:43:01 -0400

These crypto options are only selected or have been dropped from 6.16, so we drop them from our configs.

]

---

Richard,

I wasn't able to config these via a build, but by inspection and the autobuilder warning, the fix is obvious.

Apply these after my 6.16 series and the warnings should be gone.

Bruce

 meta/recipes-kernel/linux/linux-yocto-rt_6.16.bb   | 2 +-
 meta/recipes-kernel/linux/linux-yocto-tiny_6.16.bb | 2 +-
 meta/recipes-kernel/linux/linux-yocto_6.16.bb      | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)
meta/recipes-kernel/linux/linux-yocto-rt_6.16.bb +1 -1
index a5046cb38e..06d4c51a70 100644
@@ -15,7 +15,7 @@ python () {
 }
 
 SRCREV_machine ?= "0efe352ff92817ba56a91bfe983e96cd55c76940"
-SRCREV_meta ?= "1fedc277abf169c6032ea77d5d61be91dba9f0df"
+SRCREV_meta ?= "f7034ee0721badc73a0417aa324755c1e6c415e5"
 
 SRC_URI = "git://git.yoctoproject.org/linux-yocto.git;branch=${KBRANCH};name=machine;protocol=https \
            git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-6.16;destsuffix=${KMETA};protocol=https"
meta/recipes-kernel/linux/linux-yocto-tiny_6.16.bb +1 -1
index df2b0a67b2..04fb3eef42 100644
@@ -18,7 +18,7 @@ KMETA = "kernel-meta"
 KCONF_BSP_AUDIT_LEVEL = "2"
 
 SRCREV_machine ?= "f6b5e4a67c21308265aabd3cb6cf00e329d930f6"
-SRCREV_meta ?= "1fedc277abf169c6032ea77d5d61be91dba9f0df"
+SRCREV_meta ?= "f7034ee0721badc73a0417aa324755c1e6c415e5"
 
 PV = "${LINUX_VERSION}+git"
 
meta/recipes-kernel/linux/linux-yocto_6.16.bb +1 -1
index 4c070b0b2c..d19803cb6c 100644
@@ -29,7 +29,7 @@ SRCREV_machine:qemux86 ?= "f6b5e4a67c21308265aabd3cb6cf00e329d930f6"
 SRCREV_machine:qemux86-64 ?= "f6b5e4a67c21308265aabd3cb6cf00e329d930f6"
 SRCREV_machine:qemumips64 ?= "dea33382cd8394c214422ebead1a2e08a4832c90"
 SRCREV_machine ?= "f6b5e4a67c21308265aabd3cb6cf00e329d930f6"
-SRCREV_meta ?= "1fedc277abf169c6032ea77d5d61be91dba9f0df"
+SRCREV_meta ?= "f7034ee0721badc73a0417aa324755c1e6c415e5"
 
 # set your preferred provider of linux-yocto to 'linux-yocto-upstream', and you'll
 # get the <version>/base branch, which is pure upstream -stable, and the same
Signature · 1 line
2.39.2
#1 lore raw
Quoted 5 lines · Bruce Ashfield via lists.openembedded.org

From: Bruce Ashfield <[email protected]>

Integrating the following commit(s) to linux-yocto/.:

Quoted 8 lines

1/1 [
Author: Bruce Ashfield
Email: [email protected]
Subject: arm/6.16: remove unsettable and obsolete options
Date: Tue, 26 Aug 2025 22:43:01 -0400

These crypto options are only selected or have been dropped from 6.16, so we drop them from our configs.

If you still want to support CHACHA20 crypto, you should remove CONFIG_CRYPTO_CHACHA20_NEON and select CONFIG_CRYPTO_CHACHA20.

Please see this commit for a proper fix:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v6.17-rc3&id=6c9ab811871bc9a08e9cd4b96371a60667fa9ec8

#2 lore raw

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

Quoted 17 lines · Fabio Estevam
Quoted 5 lines · Bruce Ashfield via lists.openembedded.org

From: Bruce Ashfield <[email protected]>

Integrating the following commit(s) to linux-yocto/.:

Quoted 8 lines

1/1 [
Author: Bruce Ashfield
Email: [email protected]
Subject: arm/6.16: remove unsettable and obsolete options
Date: Tue, 26 Aug 2025 22:43:01 -0400

These crypto options are only selected or have been dropped from 6.16, so we drop them from our configs.

Quoted 7 lines

If you still want to support CHACHA20 crypto, you should remove CONFIG_CRYPTO_CHACHA20_NEON and select CONFIG_CRYPTO_CHACHA20.

Please see this commit for a proper fix:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v6.17-rc3&id=6c9ab811871bc9a08e9cd4b96371a60667fa9ec8

I'll leave that up to Jon/Ross. I'm just making sure there's no warning and that what I did was visible so they can make a policy call.

Thanks for the information!

Bruce

Quoted 1 line