> On Apr 28, 2020, at 1:54 AM, Anshuman Khandual <[email protected]>
> wrote:
>
> That is true. There is a slight change in the rules, making it explicit yes
> only when both ARCH_HAS_DEBUG_VM_PGTABLE and DEBUG_VM are enabled.
>
> +config DEBUG_VM_PGTABLE
> + bool "Debug arch page table for semantics compliance"
> + depends on MMU
> + depends on !IA64 && !ARM
> + depends on ARCH_HAS_DEBUG_VM_PGTABLE || EXPERT
> + default y if ARCH_HAS_DEBUG_VM_PGTABLE && DEBUG_VM
> + help
>
> The default is really irrelevant as the config option can be set explicitly.
That could also explain. Since not long time ago, it was only “default y if
DEBUG_VM”, that caused the robot saved a .config with DEBUG_VM_PGTABLE=y by
default.
Even though you changed the rule recently, it has no effect as the robot could
“make oldconfig” from the saved config for each linux-next tree execution and
the breakage will go on.
