Lines Matching full:on

8 # The recursive limitations with Kconfig has some non intuitive implications on
12 # annotate those requirements, ie, some drivers use "depends on" while others
14 # core requirement, and one uses "select" while the other uses "depends on" to
18 # A perhaps not so obvious implication of this is that, if semantics on these
20 # they select or depend on end up becoming shared requirements which cannot be
31 # due to the disjoint use of semantics on expressing each bell's relationship
32 # with CORE, one uses "depends on" while the other uses "select". Another
35 # as mandatory required symbols. For more details on the heavy handed nature
38 # To fix this the "depends on CORE" must be changed to "select CORE", or the
39 # "select CORE" must be changed to "depends on CORE".
43 # problem consisted on matching semantics with newly introduced features.
54 	depends on CORE
62 	depends on !CORE_BELL_A