summaryrefslogtreecommitdiff
path: root/tools/lib/python/kdoc/python_version.py
diff options
context:
space:
mode:
authorJulian Braha <julianbraha@gmail.com>2026-08-16 22:53:54 +0100
committerNathan Chancellor <nathan@kernel.org>2026-08-31 16:56:48 -0700
commitf9f31f5f13b5e5459e2d3322fe6b5e19d511919a (patch)
tree54d3f4978f68168200e03e26c8161aa2b6e1ba16 /tools/lib/python/kdoc/python_version.py
parentcee9395acd8043be0644b25c34bfa86623f2b935 (diff)
downloadlinux-next-f9f31f5f13b5e5459e2d3322fe6b5e19d511919a.tar.gz
linux-next-f9f31f5f13b5e5459e2d3322fe6b5e19d511919a.zip
kconfig: error out for recursive range
Currently, it is possible to create recursive ranges with Kconfig, such as: config C int "Enable C" default 1 range A B config A int "Enable A" default 2 range B C config B int "Enable B" default 3 range A C The current outcome of this example above, is that all 3 options are set to 2. There is currently no warning or error if a user attempts this. Several attributes are already checked for recursion, including 'depends on', 'select', and 'imply', and we can extend this to 'range' for numeric options (int and hex types). Recursive ranges are currently not used anywhere in the tree, so it is already safe to make this a hard error. Assisted-by: Codex:gpt-5.6-sol Signed-off-by: Julian Braha <julianbraha@gmail.com> Link: https://patch.msgid.link/20260816215354.1499059-1-julianbraha@gmail.com Signed-off-by: Nathan Chancellor <nathan@kernel.org>
Diffstat (limited to 'tools/lib/python/kdoc/python_version.py')
0 files changed, 0 insertions, 0 deletions