@@ -591,7 +591,8 @@ The two different resolutions for b) can be tested in the sample Kconfig file
591
591
Documentation/kbuild/Kconfig.recursion-issue-02.
592
592
593
593
Below is a list of examples of prior fixes for these types of recursive issues;
594
- all errors appear to involve one or more select's and one or more "depends on".
594
+ all errors appear to involve one or more "select" statements and one or more
595
+ "depends on".
595
596
596
597
============ ===================================
597
598
commit fix
@@ -653,7 +654,7 @@ the use of the xconfig configurator [1]_. Work should be done to confirm if
653
654
the deduced semantics matches our intended Kconfig design goals.
654
655
655
656
Having well defined semantics can be useful for tools for practical
656
- evaluation of depenencies , for instance one such use known case was work to
657
+ evaluation of dependencies , for instance one such case was work to
657
658
express in boolean abstraction of the inferred semantics of Kconfig to
658
659
translate Kconfig logic into boolean formulas and run a SAT solver on this to
659
660
find dead code / features (always inactive), 114 dead features were found in
@@ -680,7 +681,7 @@ abstraction the inferred semantics of Kconfig to translate Kconfig logic into
680
681
boolean formulas and run a SAT solver on it [5 ]_. Another known related project
681
682
is CADOS [6 ]_ (former VAMOS [7 ]_) and the tools, mainly undertaker [8 ]_, which
682
683
has been introduced first with [9 ]_. The basic concept of undertaker is to
683
- exract variability models from Kconfig, and put them together with a
684
+ extract variability models from Kconfig and put them together with a
684
685
propositional formula extracted from CPP #ifdefs and build-rules into a SAT
685
686
solver in order to find dead code, dead files, and dead symbols. If using a SAT
686
687
solver is desirable on Kconfig one approach would be to evaluate repurposing
0 commit comments