You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If two options cause a reassignment, but the value hasn't actually changed, we should not generate a warning.
Given the following script:
load_kconfig_unchecked(kernel_dir.."/arch/x86/configs/x86_64_defconfig")
ACPI_APEI:satisfy { y, recursive=true }
ACPI_APEI_GHES:satisfy { y, recursive=true }
ACPI_DPTF:satisfy { y, recursive=true }
ACPI_FPDT:satisfy { y, recursive=true }
ACPI_HMAT:satisfy { y, recursive=true }
BPF_LSM:satisfy { y, recursive=true }
CPU_FREQ_DEFAULT_GOV_PERFORMANCE:satisfy { y, recursive=true }
CPU_FREQ_GOV_SCHEDUTIL:satisfy { y, recursive=true }
CRASH_DUMP:set(n)
DEBUG_DEVRES:set(n)
DEBUG_INFO_REDUCED:set(n)
DEBUG_KERNEL:satisfy { y, recursive=true }
DEBUG_STACK_USAGE:set(n)
DETECT_HUNG_TASK:satisfy { y, recursive=true }
DYNAMIC_DEBUG:satisfy { y, recursive=true }
INTEL_IDLE:satisfy { y, recursive=true }
INTEL_RAPL:satisfy { m, recursive=true }
PM_ADVANCED_DEBUG:satisfy { y, recursive=true }
PM_WAKELOCKS:satisfy { y, recursive=true }
POWERCAP:satisfy { y, recursive=true }
RCU_TORTURE_TEST:set(n)
SCHEDSTATS:set(n)
SCHED_DEBUG:satisfy { y, recursive=true }
SUNRPC_DEBUG:satisfy { y, recursive=true }
X86_AMD_PSTATE:satisfy { y, recursive=true }
X86_INTEL_LPSS:satisfy { y, recursive=true }
X86_INTEL_PSTATE:satisfy { y, recursive=true }
You see this warning:
linux-config> warning: reassignment of symbol POWERCAP to Tristate(Yes)
linux-config> --> /nix/store/ivr7bxami3pcbmvlbvvc0nbmbjk0by98-linux-6.1.13-autokernel.lua:18
linux-config> |
linux-config> 18 | INTEL_RAPL:satisfy { m, recursive = true }
linux-config> | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: previously assigned here to Tristate(Yes)
linux-config> | hint: this did not change the previous value Boolean(true)
linux-config> |
linux-config> 21 | POWERCAP:satisfy { y, recursive = true }
linux-config> | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: reassigned here to Tristate(Yes)
linux-config> | hint: this did not change the previous value Boolean(true)
linux-config> |
But no actual reassignment is taking place, since both eval to Boolean(true)
The text was updated successfully, but these errors were encountered:
If two options cause a reassignment, but the value hasn't actually changed, we should not generate a warning.
Given the following script:
You see this warning:
But no actual reassignment is taking place, since both eval to
Boolean(true)
The text was updated successfully, but these errors were encountered: