summaryrefslogtreecommitdiffstats
path: root/config
Commit message (Collapse)AuthorAgeFilesLines
* config: Use APK as package manager by defaultPaul Spooren11 days1-0/+1
| | | | | | | | | | This commit comes after a long period of hard work, starting back in early 2021 as a proof of concept. Thanks to the Alpine Linux project for creating such a nice package manager. Thanks to everyone involved; this is going to be great! Signed-off-by: Paul Spooren <mail@aparcar.org>
* menuconfig: add help description for Stack Smashing Protection optionsMarius Dinu11 days1-0/+18
| | | | | | | | | Descriptions taken from: https://wiki.osdev.org/Stack_Smashing_Protector Signed-off-by: Marius Dinu <m95d+git@psihoexpert.ro> Link: https://github.com/openwrt/openwrt/pull/16897 Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
* kernel: KERNEL_NET_L3_MASTER_DEV default to y if !SMALL_FLASHPaul Donald2024-11-011-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Follow-up for 45d541bb409355f090b971d96ebebd8610ef84a7 This change allows features such as kmod-vrf ``` KERNEL_NET_L3_MASTER_DEV=n x86_64 generic bzImage 6,927,360 bytes aarch64 coretex-a53 kernel 4,268,836 bytes KERNEL_NET_L3_MASTER_DEV=y x86_64 generic bzImage 6,931,456 bytes aarch64 coretex-a53 kernel 4,273,042 bytes Delta: x86_64 generic +4096 bytes aarch64 coretex-a53 +4206 bytes x86_64 generic vrf.ko - 258,792 bytes aarch64 coretex-a53 vrf.ko - 263,632 bytes ``` See: https://forum.openwrt.org/t/vrf-support-testing-out-evpn-at-home/181108 https://forum.openwrt.org/t/please-enable-net-l3-master-dev-in-kernel-build-by-default/201825 Signed-off-by: Paul Donald <newtwen+github@gmail.com> Link: https://github.com/openwrt/openwrt/pull/16819 Signed-off-by: Robert Marko <robimarko@gmail.com>
* kernel: enable Multi-Path TCP for !SMALL_FLASH targetsDaniel Golle2024-10-261-0/+14
| | | | | | | | | | | | | | | | | | Expose Kernel's CONFIG_MPTCP option and enable it by default for !SMALL_FLASH targets. The idea behind enabling it by default is to allow users of the binary distribution to make use of MPTCP tunneling for link aggregation. Using MPTCP for link aggregation is an often discussed topic in the forum and there is even a whole OpenWrt fork (MPTCPRouter) just for that. Enabling the kernel-side of the story by default will allow using MPTCP on vanilla OpenWrt without having to build anything from source. See also https://openwrt.org/docs/guide-user/network/mptcp Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* config: build: make STRIP_KERNEL_EXPORTS depend on BROKENRobert Marko2024-09-211-1/+1
| | | | | | | | | STRIP_KERNEL_EXPORTS is currently broken on kernel 6.6 and since this is the only kernel currently supported, we should rather make it depend on BROKEN instead of a kernel version until its fixed. Link: https://github.com/openwrt/openwrt/pull/16440 Signed-off-by: Robert Marko <robimarko@gmail.com>
* kernel: Activate POSIX ACL for f2fs, jffs2 and tmpfsHauke Mehrtens2024-09-061-2/+5
| | | | | | | | | When CONFIG_USE_FS_ACL_ATTR is set we will also activate POSIX ACL support for the f2fs, jffs2 and tmpfs file system. This option is activated on all targets with big flash. Link: https://github.com/openwrt/openwrt/pull/16181 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: activate *_FS_SECURITY and *_FS_ACL_ATTR options for all big flash ↵Leo Barsky2024-09-061-0/+5
| | | | | | | | | | | | | targets This patch activate *_FS_SECURITY and *_FS_ACL_ATTR options for all big flash memory targets. Fixes docker error: "failed to register layer: lsetxattr security.capability /usr/bin/ping: operation not supported" Forum discussion: https://forum.openwrt.org/t/docker-pull-fails-failed-to-register-layer-operation-not-supported/138253 Signed-off-by: Leo Barsky <leobrsky@proton.me> Link: https://github.com/openwrt/openwrt/pull/16181 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* config: kernel: Add support for configuring BTRFS to be built-inMarek Behún2024-08-151-0/+6
| | | | | | | | | | | | | | | | | | Add the KERNEL_BTRFS_FS config option so that targets can select whether BTRFS support must be built-in. Select this option (alongside KERNEL_BTRFS_FS_POSIX_ACL) from the layerscape/armv8_64b subtarget instead of enabling it in target/linux/layerscape/armv8_64b/config-* files. Move disabling of CONFIG_BTRFS_FS_CHECK_INTEGRITY into generic configs. This makes it possible for OpenWRT to be built with built-in BTRFS support on specific boards, instead of whole targets. Signed-off-by: Marek Behún <kabel@kernel.org> Link: https://github.com/openwrt/openwrt/pull/15990 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: add missing symbolStijn Tintel2024-08-031-0/+4
| | | | | | | | | Enabling KERNEL_DEBUG_INFO_BTF and KERNEL_KPROBE_EVENTS on 6.6 exposes CONFIG_PROBE_EVENTS_BTF_ARGS in the kernel config. Add a build option for it to fix build failures with KERNEL_DEBUG_INFO_BTF and KERNEL_KPROBE_EVENTS enabled on targets using the 6.6 kernel. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* apk: limit CONFIG_IPK_FILES_CHECKSUMS config to OPKGChristian Marangi2024-06-201-0/+1
| | | | | | | Limit CONFIG_IPK_FILES_CHECKSUMS config to OPKG as APK have different way to validate package integrity (apk audit) Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
* Revert "apk: limit CONFIG_IPK_FILES_CHECKSUMS config to OPKG"Christian Marangi2024-06-201-1/+0
| | | | | | | | | This reverts commit 25bbefcdd9424ed1b6ef35a39e84420fc4cce322. Only the Config-build.in change needed to be merged and this contains leftover from previous revision of the feature. Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
* config: imply apk-mbedtls with USE_APKChristian Marangi2024-06-111-0/+1
| | | | | | | | | | | | On top of the fixup to select apk-mbedtls when USE_APK is enabled from a new config, also imply the package when enabling the config to catch .config that are already init. (Having both opkg and apk installed in a system is not a problem but if USE_APK is used, APK presence in the system is mandatory) Link: https://github.com/openwrt/openwrt/pull/15543 Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
* apk: limit CONFIG_IPK_FILES_CHECKSUMS config to OPKGChristian Marangi2024-06-111-0/+1
| | | | | | | | Limit CONFIG_IPK_FILES_CHECKSUMS config to OPKG as APK have different way to validate package integrity (apk audit) Link: https://github.com/openwrt/openwrt/pull/15543 Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
* config: kernel: remove KASAN_EXTRAQingfang Deng2024-06-071-10/+0
| | | | | | The option has been removed from the kernel since 5.1. Signed-off-by: Qingfang Deng <dqfext@gmail.com>
* build: add option KERNEL_DEBUG_INFO_BTF_MODULESTony Ambardar2024-05-311-2/+5
| | | | | | | | | | | | The recent kernel v6.6.31 update broke BTF-enabled builds since upstream Linux added a prompt for config option DEBUG_INFO_BTF_MODULES in commit 2166cb2e21 ("bpf, kconfig: Fix DEBUG_INFO_BTF_MODULES Kconfig definition"). Fix by updating Config-kernel.in to add the option, cleaning up a related dependency and whitespace also. Fixes: 10d77b9bc3 ("kernel: bump 6.6 to 6.6.31") Signed-off-by: Tony Ambardar <itugrok@yahoo.com>
* build: add APK package build capabilitiesPaul Spooren2024-05-171-0/+3
| | | | | | | | | A new option called `USE_APK` is added which generated APK packages (.apk) instead of OPKG packages (.ipk). Some features like fstools `snapshot` command are not yet ported Signed-off-by: Paul Spooren <mail@aparcar.org>
* config: build: dont allow STRIP_KERNEL_EXPORTS on kernel 6.6Robert Marko2024-05-161-0/+1
| | | | | | | | | | | | STRIP_KERNEL_EXPORTS is currently not working on kernel 6.6 as there have been major changes in the upstream kernel. I have looked at it, and I dont think we can adapt the current patch to work so until this is fixed lets prevent STRIP_KERNEL_EXPORTS from being selected on 6.6. Link: https://github.com/openwrt/openwrt/pull/15498 Signed-off-by: Robert Marko <robimarko@gmail.com>
* config: add ARM PMUv3 for kernel 6.6Robert Marko2024-05-141-0/+6
| | | | | | | | | | | | | Kernel 6.6 has moved the ARM PMUv3 driver to drivers/perf and now once KERNEL_ARM_PMU is selected trying to build the kernel will stop with: ARM PMUv3 support (ARM_PMUV3) [N/y/?] (NEW) So, lets enable ARM_PMUV3 for ARMv7 and ARMv8 architectures if KERNEL_PERF_EVENTS is selected. Fixes: #15466 Link: https://github.com/openwrt/openwrt/pull/15469 Signed-off-by: Robert Marko <robimarko@gmail.com>
* loongarch64: new targetWeijie Gao2024-05-041-4/+6
| | | | | | | | | | | | | | | | | | | | | | | | Add target for Loongson LoongArch64-based boards. LoongArch is a new RISC ISA developed by Loongson. It's a bit like MIPS or RISC-V. LoongArch includes both 32-bit and 64-bit versions (LoongArch32/LoongArch64). Loongson 3A5000 and 3A6000 are the two existing CPUs of LoongArch64 and is used for PC products. It's BIOS supports ACPI and UEFI-only boot. These CPUs supports SMP and SMT. At present only LoongArch64 is supported by linux kernel. Toolchain requirement: binutils >= 2.40 gcc >= 13.1 For details, please check the following links: https://lwn.net/Articles/861951/ https://loongson.github.io/LoongArch-Documentation/README-EN.html Signed-off-by: Weijie Gao <hackpascal@gmail.com>
* mediatek: increase size of the sdcard image to 512 MiBDaniel Golle2024-05-021-0/+1
| | | | | | | | | | | | | | | | | | | | | Increasing the size of the rootfs_data filesystem has become a ever repeating discussion and seems to be the most important thing for users of the MediaTek-based BananaPi boards. Using the whole remaining size of a microSD or the eMMC for rootfs_data doesn't make sense for many reasons, but neither does the current default of 104 MiB for the 'rootfs' partition size. Increase the 'rootfs' partition size to 448 MiB which will result in the sdcard image being exactly 512 MiB. Finding a microSD card smaller than 512 MiB and still working could anyway be difficult in 2024. That will allow users to install even bloatware written in Go or other space-hungry languages while still leaving most of the space unallocated for additional partitions or volumes to be used for persistent user data. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* config: select KERNEL_WERROR if building with default GCC versionDaniel Golle2024-04-081-2/+0
| | | | | | | | | | | | | | | | At the moment we have to manually follow the default GCC version also in config/Config-kernel.in. This tends to be forgotten at GCC version bumps (just happened when switching from version 12 to 13). Instead, introduce a hidden Kconfig symbol which implies KERNEL_WERROR in toolchain/gcc/Config.in where it is visible for developers changing the default version. Also remove the explicit default on BUILDBOT to avoid a circular dependency and also because buildbots anyway implicitly always select the default GCC version. Reference: https://github.com/openwrt/openwrt/pull/15064 Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* config: Enable ext4 journaling by default.Jordan Woyak2024-03-291-0/+1
| | | | | | | | | | Not having a journal by default is a major "gotcha". Because openwrt does not fsck on boot, a power loss without journaling can result in a dirty filesystem that openwrt will mount as read-only which requires intervention to restore the router to working order. Signed-off-by: Jordan Woyak <jordan.woyak@gmail.com>
* kernel: support RISC-V PMUQingfang Deng2024-03-231-0/+10
| | | | | | Add RISC-V PMU config symbols and enable them for riscv64. Signed-off-by: Qingfang Deng <dqfext@gmail.com>
* kernel: enable KASAN option for more architecturesQingfang Deng2024-03-081-1/+1
| | | | | | | KASAN has supported more architectures, such as ARM, PPC32 and RISC-V 64. Enable KASAN option for those architectures. Signed-off-by: Qingfang Deng <dqfext@gmail.com>
* broadcom-wl: remove packageFelix Fietkau2024-02-031-15/+0
| | | | | | | Also remove remaining wireless extension support, since this package was the only in-tree user of it Signed-off-by: Felix Fietkau <nbd@nbd.name>
* build: add option for building with stack-protector-allCedric DOURLENT2024-01-191-0/+2
| | | | | | | | | | | | | The GCC option -fstack-protector-all is a security feature used to protect against stack-smashing attacks. This option enhances the stack-smashing protection provided by -fstack-protector-strong. -fstack-protector-all option applies stack protection to all functions, regardless of their characteristics. While this offers the most comprehensive protection against stack-smashing attacks, it can significantly impact the performance of the program because every function call includes additional checks for stack integrity. This option can incur a performance penalty because of the extra checks added to every function call, but it significantly enhances security, making it harder for attackers to exploit buffer overflows to execute arbitrary code. It's particularly useful in scenarios where security is paramount and performance trade-offs are acceptable. Signed-off-by: Cedric DOURLENT <cedric.dourlent@softathome.com>
* target: Make TARGET_SERIAL independent of GRUB configurationHauke Mehrtens2023-11-291-6/+7
| | | | | | | | | | | | | GRUB_SERIAL is also used for the default serial on the target and not only in grub. When no grub was build it was not available and the build fails. Rename GRUB_SERIAL to TARGET_SERIAL and make it always available on x86 and armsr targets. Fixes: #14063 Fixes: b10768476f9d ("x86,armsr: interpolate GRUB_SERIAL into /etc/inittab") Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: provide better control & help for SLUB configurationRafał Miłecki2023-11-091-2/+15
| | | | | | | Allow selecting KERNEL_SLUB_DEBUG and KERNEL_SLUB_DEBUG_ON manually and provide detailed help for both. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* build: add CycloneDX SBOM JSON supportPetr Štetiar2023-11-011-0/+8
| | | | | | | | | | | | | CycloneDX is an open source standard developed by the OWASP foundation. It supports a wide range of development ecosystems, a comprehensive set of use cases, and focuses on automation, ease of adoption, and progressive enhancement of SBOMs (Software Bill Of Materials) throughout build pipelines. So lets add support for CycloneDX SBOM for packages and images manifests. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* kernel: default ARM_PMU on for armsr/armv8Mathew McBride2023-08-151-0/+1
| | | | | | | | CONFIG_ARM_PMU (Arm Performance Monitor Unit) is a requirement to use KVM (virtualization) from Linux 5.11+, as the virtualised guest has virtualized PMU access. Signed-off-by: Mathew McBride <matt@traverse.com.au>
* build: Add option KERNEL_KASAN_SW_TAGS and HW_TAGSZhen XIN2023-08-101-4/+61
| | | | | | | | | | | | | Currently KASAN is supported but only the generic one. SW-tag and HW-tag based KASAN have less impact on memory footprint or performance, and are worth supporting. Add choice menu for software and hardware Tag-Based KASAN, in addition to the generic one. Signed-off-by: Zhen XIN <zhen.xin@nokia-sbell.com> [Restructure commit message] Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: modules: add xdp-sockets-diag supportTianling Shen2023-07-051-0/+6
| | | | | | Support for PF_XDP sockets monitoring interface used by the ss tool. Signed-off-by: Tianling Shen <cnsztl@immortalwrt.org>
* config: add a knob to use the mold linker for packagesAndre Heider2023-07-042-1/+26
| | | | | | | | | Building it requires gcc >= 10.2 or clang >= 12. Using sstrip with its -z argument can produce non-working binaries, like a segfaulting `getrandom`, so don't allow that combination. Signed-off-by: Andre Heider <a.heider@gmail.com>
* build: replace SSTRIP_ARGS with SSTRIP_DISCARD_TRAILING_ZEROESAndre Heider2023-07-041-6/+4
| | | | | | | | | sstrip only has one functional arg. Make that a bool option, which can easily depend on other knobs then. This is required to be disabled for the mold linker. Signed-off-by: Andre Heider <a.heider@gmail.com>
* kernel: introduce KERNEL_WERROR config optionPetr Štetiar2023-07-041-0/+16
| | | | | | | | | | | | | In commit b2d1eb717b65 ("generic: 5.15: enable Werror by default for kernel compile") CONFIG_WERROR=y was enabled and all warnings/errors reported with GCC 12 were fixed. Keeping this in sync with past/future GCC versions is going to be uphill battle, so lets introduce new KERNEL_WERROR config option, enable it by default only for tested/known working combinations and on buildbots. References: #12687 Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ipq807x: rename target to qualcommaxRobert Marko2023-06-161-1/+1
| | | | | | | | | | | | | Currently, ipq807x only covers Qualcomm IPQ807x SoC-s. However, Qualcomm also has IPQ60xx and IPQ50xx SoC-s under the AX WiSoC-s and they share a lot of stuff with IPQ807x, especially IPQ60xx so to avoid duplicating kernel patches and everything lets make a common target with per SoC subtargets. Start doing that by renaming ipq807x to qualcommax so that dependencies on ipq807x target can be updated. Signed-off-by: Robert Marko <robimarko@gmail.com>
* config: change references from armvirt to armsrMathew McBride2023-06-101-5/+5
| | | | | | | armvirt target has been renamed to armsr (Arm SystemReady), so the config defaults need to be changed as well. Signed-off-by: Mathew McBride <matt@traverse.com.au>
* build: enable vmdk/vmware images for arm64 targetMathew McBride2023-06-021-1/+1
| | | | | | This is useful for VMware's ARM64 products, e.g Fusion for M1/ARM Macs. Signed-off-by: Mathew McBride <matt@traverse.com.au>
* build: use 128MiB as the boot/kernel partition size on armvirt targetMathew McBride2023-06-021-0/+1
| | | | | | | | | | | | | | | | The nominal partition type for EFI boot partitions is FAT32, which has a minimum size of 32MiB on a 512-byte-sector block device. To ensure that the boot partition is created as FAT32 set a size well above this minimum. A useful discussion about EFI partition sizes can be found here: https://superuser.com/questions/1310927/what-is-the-absolute-minimum-size-a-uefi-system-partition-can-be I have found 128MiB works pretty consistently across both tools (mkfs.fat) and firmwares (EDKII) Signed-off-by: Mathew McBride <matt@traverse.com.au>
* grub2: enable EFI for armvirtMathew McBride2023-06-021-4/+5
| | | | | | | | | | | This adds a separate package for EFI on Arm SystemReady compatible machines. 32-bit Arm UEFI is supported as well. It is very similar to x86-64 EFI setup, without the need for BIOS backward compatibility and slightly different default modules. Signed-off-by: Mathew McBride <matt@traverse.com.au>
* kernel: Set CONFIG_FRAME_WARN depending on targetHauke Mehrtens2023-06-021-0/+11
| | | | | | | | This set the CONFIG_FRAME_WARN option depending on some target settings. It will use the default from the upstream kernel and not the hard coded value of 1024 now. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: add MODULE_ALLOW_BTF_MISMATCH optionTianling Shen2023-05-181-0/+10
| | | | | | | | | | | BTF mismatch can occur for a separately-built module even when the ABI is otherwise compatible and nothing else would prevent successfully loading. Add a new config to control how mismatches are handled. By default, preserve the current behavior of refusing to load the module. If MODULE_ALLOW_BTF_MISMATCH is enabled, load the module but ignore its BTF information. Signed-off-by: Tianling Shen <cnsztl@immortalwrt.org>
* treewide: cleanup kernel symbol referencesNick Hainke2023-05-121-1/+0
| | | | | | | | | | | | | | | We only use 5.15 kernel. So remove all those unnecessary symbols referencing 5.10 or 5.15 kernel. Can be found with: git grep -E 'LINUX_5_1(0|5)' Note that we remove the dependency from "sound-soc-chipdip-dac" instead of removing the complete kernel package. The 5.15 version bump forgot to delete the "@LINUX_5_10" dependency. The kernel package is still needed in 5.15 kernel. Signed-off-by: Nick Hainke <vincent@systemli.org>
* kernel: improve handling of CONFIG_IO_URINGTony Ambardar2023-05-031-1/+2
| | | | | | | | | | | | | | | | | | | | | | Kernel setting CONFIG_IO_URING supports high-performance I/O for file access and servers, generally for more performant platforms, and adds ~45 KB to kernel sizes. The need for this on less "beefy" devices is questionable, as is the size cost considering many platforms have kernel size limits which require tricky repartitioning if outgrown. The size cost is also large relative to the ~180 KB bump expected between major OpenWRT kernel releases. No OpenWrt packages have hard dependencies on this; samba4 and mariadb can take advantage if available (+KERNEL_IO_URING:liburing) but otherwise build and work fine. Since CONFIG_IO_URING is already managed via the KERNEL_IO_URING setting in Config-kernel.in (default Y), remove it from those target configs which unconditionally enable it, and update the defaults to enable it conditionally only on more powerful 64-bit x86 and arm devices. It may still be manually enabled as needed for high-performance custom builds. Signed-off-by: Tony Ambardar <itugrok@yahoo.com>
* build: add a config knob to enable LTO for all packagesAndre Heider2023-03-211-0/+7
| | | | | | This enables LTO for all packages which haven't opted-out. Signed-off-by: Andre Heider <a.heider@gmail.com>
* build: add a config knob to enable gc-sections for all packagesAndre Heider2023-03-211-0/+8
| | | | | | | This enables the linker's garbage collection for all packages which haven't opted-out. Signed-off-by: Andre Heider <a.heider@gmail.com>
* kernel: Add CONFIG_KERNEL_HARDLOCKUP_DETECTORHauke Mehrtens2023-03-191-0/+12
| | | | | | | Make it possible to change the kernel configuration option CONFIG_HARDLOCKUP_DETECTOR from OpenWrt. Signed-off-by: Hauke Mehrtens <hmehrtens@maxlinear.com>
* kernel: set default for KERNEL_BPF_KPROBE_OVERRIDEStijn Tintel2023-03-051-0/+1
| | | | | | | | | Without the default value this still causes a missing symbol. Disable by default as it depends on FUNCTION_ERROR_INJECTION, which is disabled in the generic config and we don't have a build symbol to enable that. Fixes: 500c37c56ff6 ("kernel: add missing symbol") Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* build: fix for sourcing targets image config installed via feedsPrasun Maiti2023-02-261-0/+1
| | | | | | | | Sourcing of image/Config.in will not happen When a target is installed from target/linux/feeds/ Signed-off-by: Prasun Maiti <prasunmaiti87@gmail.com> Acked-by: Petr Štetiar <ynezz@true.cz>
* kernel: set default values for ARM low level debugging symbolsRobert Marko2023-02-081-0/+6
| | | | | | | | | | | | | | | | | | | | | Set default values for KERNEL_DEBUG_LL and KERNEL_DEBUG_LL_UART_NONE again as both of these symbols are non visible if KERNEL_EARLY_PRINTK is not selected and KConfig wont write their value to .config. This usually is the intended behaviour, but in OpenWrt we are relying on the KConfig to set these and disable the debug console settings that multiple targets like mvebu have set in their kernel config. This was the behaviour before removing all of the "default n" settings as KConfig by default considers symbols disabled but they are not visible anymore and thus their value is not set in .config and build system then later does not override the values from target kernel config. So, to restore the behaviour to the previous one lets a default value for KERNEL_DEBUG_LL and KERNEL_DEBUG_LL_UART_NONE. Fixes: 8bc72ea7be39 ("treewide: strip useless default n Kconfig lines") Tested-by: Georgi Valkov <gvalkov@gmail.com> Signed-off-by: Robert Marko <robimarko@gmail.com>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-21 12:06:21 +0000