Mieczyslaw Nalewaj 5213918c3d ramips: restore CONFIG_PAGE_BLOCK_MAX_ORDER=10 for 6.18 ... Restore CONFIG_PAGE_BLOCK_MAX_ORDER=10 in ramips 6.18 config fragments to fix build failures where PAGE_BLOCK_MAX_ORDER was undefined. Support for Linux 6.18 on ramips was added after this OpenWrt change: ac0cb87a45. Before that integration, the kernel option CONFIG_PAGE_BLOCK_MAX_ORDER=10 was provided in target/linux/generic/config-6.18 and applied broadly. After the ramips 6.18 integration the generic fragment no longer supplied this option for ramips targets, which caused some backported code paths and drivers to assume PAGE_BLOCK_MAX_ORDER was defined and led to compilation failures. Signed-off-by: Mieczyslaw Nalewaj <namiltd@yahoo.com> Link: https://github.com/openwrt/openwrt/pull/22831 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>		2026-04-08 00:00:24 +02:00
..
base-files	treewide: remove execute bit and shebang from board.d files	2021-03-06 11:30:06 +01:00
config-6.12	kernel/ramips: restore files for v6.12	2026-04-06 11:26:27 +02:00
config-6.18	ramips: restore CONFIG_PAGE_BLOCK_MAX_ORDER=10 for 6.18	2026-04-08 00:00:24 +02:00
target.mk	treewide: replace wpad-basic-wolfssl default	2023-02-04 02:35:03 +01:00