Propagate dependencies to range conditions

Just like for other properties, conditions on ranges get local
'depends on' and parent dependencies propagated to them. Oversight.

Did not trigger any deviations for the kernel defconfigs. Pretty
specific circumstances were required for breakage, like a symbol
depending on the particular value of a symbol with a 'range' and parent
deps 'n', or a symbol with ranges being defined in multiple locations
with different parent deps.

(There is one symbol that both has ranges and is defined in multiple
locations: BCH_CONST_M. The second definition adds a default rather than
a range though.)

0 files changed, 0 insertions, 0 deletions