[U-Boot] why two "config FIT_VERBOSE" lines in top-level Kconfig?

weird ...
config FIT_VERBOSE bool "Display verbose messages on FIT boot" depends on FIT
... jump to a bit lower down ...
config FIT_VERBOSE bool "Show verbose messages when FIT images fails" depends on FIT help Generally a system will have valid FIT images so debug messages are a waste of code space. If you are debugging your images then you can enable this option to get more verbose information about failures.
this is really a lead-in to a larger question -- any objection to refactoring some of the Kconfig files that have numerous identical dependency lines which could be replaced by a simpler "if" test?
that top-level Kconfig file is a candidate, given the number of "depends on FIT" lines that could be removed and surrounded by:
if FIT ... endif
and some Kconfig files have entries in a weird order such that, if you select a feature, dependent features suddenly pop up somewhere else in the display, a bit disconcerting.
anyway, i'll post a refactored top-level Kconfig, so people can see what i'm talking about.
rday
participants (1)
-
Robert P. J. Day