]> git.ipfire.org Git - thirdparty/openwrt.git/commit
ramips: restore CONFIG_PAGE_BLOCK_MAX_ORDER=10 for 6.18 22831/head
authorMieczyslaw Nalewaj <namiltd@yahoo.com>
Tue, 7 Apr 2026 17:12:37 +0000 (19:12 +0200)
committerHauke Mehrtens <hauke@hauke-m.de>
Tue, 7 Apr 2026 22:00:24 +0000 (00:00 +0200)
commit5213918c3d955b3f4ad796fe8cf0ce06aaf5ccbc
treef30bbe3cf2f3ff0a1276bc81ba054d4df74f641e
parentdb68b8cefacfff36b70af12d8d9d0e6231fd7ac2
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:
https://github.com/openwrt/openwrt/commit/ac0cb87a453698efc6c812e4f27cadbeb208f14e.
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>
target/linux/ramips/mt7620/config-6.18
target/linux/ramips/mt7621/config-6.18
target/linux/ramips/mt76x8/config-6.18
target/linux/ramips/rt288x/config-6.18
target/linux/ramips/rt305x/config-6.18
target/linux/ramips/rt3883/config-6.18