diff mbox series

linux-yocto/6.16: cfg fix configuration audit warnings

Message ID 20250827024658.2076887-1-bruce.ashfield@gmail.com
State New
Headers show
Series linux-yocto/6.16: cfg fix configuration audit warnings | expand

Commit Message

Bruce Ashfield Aug. 27, 2025, 2:46 a.m. UTC
From: Bruce Ashfield <bruce.ashfield@gmail.com>

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

1/1 [
    Author: Bruce Ashfield
    Email: bruce.ashfield@gmail.com
    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.

    Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
]

Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
---

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(-)

Comments

Fabio Estevam Aug. 27, 2025, 4:02 a.m. UTC | #1
On Tue, Aug 26, 2025 at 11:47 PM Bruce Ashfield via
lists.openembedded.org
<bruce.ashfield=gmail.com@lists.openembedded.org> wrote:
>
> From: Bruce Ashfield <bruce.ashfield@gmail.com>
>
> Integrating the following commit(s) to linux-yocto/.:
>
> 1/1 [
>     Author: Bruce Ashfield
>     Email: bruce.ashfield@gmail.com
>     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
Bruce Ashfield Aug. 27, 2025, 11:29 a.m. UTC | #2
- Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end
- "Use the force Harry" - Gandalf, Star Trek II


On Wed, Aug 27, 2025, 1:02 AM Fabio Estevam <festevam@gmail.com> wrote:

> On Tue, Aug 26, 2025 at 11:47 PM Bruce Ashfield via
> lists.openembedded.org
> <bruce.ashfield=gmail.com@lists.openembedded.org> wrote:
> >
> > From: Bruce Ashfield <bruce.ashfield@gmail.com>
> >
> > Integrating the following commit(s) to linux-yocto/.:
> >
> > 1/1 [
> >     Author: Bruce Ashfield
> >     Email: bruce.ashfield@gmail.com
> >     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



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




>
diff mbox series

Patch

diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_6.16.bb b/meta/recipes-kernel/linux/linux-yocto-rt_6.16.bb
index a5046cb38e..06d4c51a70 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_6.16.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_6.16.bb
@@ -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"
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_6.16.bb b/meta/recipes-kernel/linux/linux-yocto-tiny_6.16.bb
index df2b0a67b2..04fb3eef42 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_6.16.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_6.16.bb
@@ -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"
 
diff --git a/meta/recipes-kernel/linux/linux-yocto_6.16.bb b/meta/recipes-kernel/linux/linux-yocto_6.16.bb
index 4c070b0b2c..d19803cb6c 100644
--- a/meta/recipes-kernel/linux/linux-yocto_6.16.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_6.16.bb
@@ -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