From: Bruce Ashfield Date: Wed, 10 Sep 2025 19:39:42 +0000 (-0400) Subject: linux-yocto/6.16: cfg: fix audit warnings X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=0778acc56fa18e2af9cc090eddccf33914926be7;p=thirdparty%2Fopenembedded%2Fopenembedded-core-contrib.git linux-yocto/6.16: cfg: fix audit warnings Integrating the following commit(s) to linux-yocto/.: 1/4 [ Author: Bruce Ashfield Email: bruce.ashfield@gmail.com Subject: guest: make DRM guest options arch specific Date: Wed, 10 Sep 2025 13:38:37 -0400 We only need some of the extended DRM options if the guest is x86-64 or arm64, otherwise, we get configuration warnings as the options are not valid. Restrict the architectures and we get a clean configuration and can build packages like vboxguestdrivers. Signed-off-by: Bruce Ashfield ] 2/4 [ Author: Bruce Ashfield Email: bruce.ashfield@gmail.com Subject: debug-sched: drop SCHED_DEBUG Date: Wed, 10 Sep 2025 14:51:19 -0400 Yes, we could drop the entire fragment, but then users of it would get config errors unessarily. We keep it to ensure that CONFIG_PROC is around in small configurations. This is dropped due to: commit b52173065e0aad82a31863bb5f63ebe46f7eb657 Author: Ingo Molnar Date: Mon Mar 17 11:42:56 2025 +0100 sched/debug: Remove CONFIG_SCHED_DEBUG For more than a decade, CONFIG_SCHED_DEBUG=y has been enabled in all the major Linux distributions: /boot/config-6.11.0-19-generic:CONFIG_SCHED_DEBUG=y The reason is that while originally CONFIG_SCHED_DEBUG started out as a debugging feature, over the years (decades ...) it has grown various bits of statistics, instrumentation and control knobs that are useful for sysadmin and general software development purposes as well. But within the kernel we still pretend that there's a choice, and sometimes code that is seemingly 'debug only' creates overhead that should be optimized in reality. So make it all official and make CONFIG_SCHED_DEBUG unconditional. Now that all uses of CONFIG_SCHED_DEBUG are removed from the code by previous patches, remove the Kconfig option as well. Signed-off-by: Ingo Molnar Tested-by: Shrikanth Hegde Cc: Peter Zijlstra Cc: Juri Lelli Cc: Vincent Guittot Cc: Dietmar Eggemann Cc: Steven Rostedt Cc: Ben Segall Cc: Mel Gorman Cc: Valentin Schneider Cc: Linus Torvalds Link: https://lore.kernel.org/r/20250317104257.3496611-6-mingo@kernel.org Signed-off-by: Bruce Ashfield ] 3/4 [ Author: Bruce Ashfield Email: bruce.ashfield@gmail.com Subject: x86: drop CONFIG_HIGHPTE Date: Wed, 10 Sep 2025 15:05:46 -0400 commit 0081fdeccbf610499b79784998b1fd36783209dd Author: Arnd Bergmann Date: Wed Feb 26 22:37:11 2025 +0100 x86/mm: Drop support for CONFIG_HIGHPTE With the maximum amount of RAM now 4GB, there is very little point to still have PTE pages in highmem. Drop this for simplification. The only other architecture supporting HIGHPTE is 32-bit arm, and once that feature is removed as well, the highpte logic can be dropped from common code as well. Signed-off-by: Arnd Bergmann Signed-off-by: Ingo Molnar Cc: Linus Torvalds Link: https://lore.kernel.org/r/20250226213714.4040853-8-arnd@kernel.org Signed-off-by: Bruce Ashfield ] 4/4 [ Author: Bruce Ashfield Email: bruce.ashfield@gmail.com Subject: hostap: drop obselete LIB80211 Date: Wed, 10 Sep 2025 15:19:37 -0400 These options are no longer valid in 6.16+ commit 02f220b5267042d0de649614eec84ded8aeecb4f Author: Johannes Berg Date: Mon Oct 7 20:26:55 2024 +0200 wifi: ipw2x00/lib80211: move remaining lib80211 into libipw There's already much code in libipw that used to be shared with more drivers, but now with the prior cleanups, those old Intel ipw2x00 drivers are also the only ones using whatever is now left of lib80211. Move lib80211 entirely into libipw. Link: https://patch.msgid.link/20241007202707.915ef7b9e7c7.Ib9876d2fe3c90f11d6df458b16d0b7d4bf551a8d@changeid Signed-off-by: Johannes Berg Signed-off-by: Bruce Ashfield ] Signed-off-by: Bruce Ashfield Signed-off-by: Richard Purdie --- 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 7725bcf20b..b86748d7d5 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 ?= "c631c6cf05de829937afe048e6ae2fea15634cc8" -SRCREV_meta ?= "5b4b90bbad3ada455c7c124bf704c519c6013aa1" +SRCREV_meta ?= "6cd9824a84b5fd5c8557208a787252e31a063436" 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 befced7a98..254e6727fe 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 ?= "01bcf423b031a36a070c7a983e45992e634fceb7" -SRCREV_meta ?= "5b4b90bbad3ada455c7c124bf704c519c6013aa1" +SRCREV_meta ?= "6cd9824a84b5fd5c8557208a787252e31a063436" 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 2ea54a5301..a773d8a426 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 ?= "01bcf423b031a36a070c7a983e45992e634fceb7" SRCREV_machine:qemux86-64 ?= "01bcf423b031a36a070c7a983e45992e634fceb7" SRCREV_machine:qemumips64 ?= "2459c29bf2c3d221fd6d3222c7200b368156986e" SRCREV_machine ?= "01bcf423b031a36a070c7a983e45992e634fceb7" -SRCREV_meta ?= "5b4b90bbad3ada455c7c124bf704c519c6013aa1" +SRCREV_meta ?= "6cd9824a84b5fd5c8557208a787252e31a063436" # set your preferred provider of linux-yocto to 'linux-yocto-upstream', and you'll # get the /base branch, which is pure upstream -stable, and the same