diff options
| author | Nicolas Pitre <nicolas.pitre@linaro.org> | 2017-11-17 04:06:39 +0300 |
|---|---|---|
| committer | Masahiro Yamada <yamada.masahiro@socionext.com> | 2018-01-05 20:31:23 +0300 |
| commit | 9059a3493efea6492451430c7e2fa0af799a2abb (patch) | |
| tree | bc3011bb806742c6b1f2f4d8b13692aebb51a844 /scripts/genksyms/parse.tab.c_shipped | |
| parent | cfe17c9bbe6a673fdafdab179c32b355ed447f66 (diff) | |
| download | linux-9059a3493efea6492451430c7e2fa0af799a2abb.tar.xz | |
kconfig: fix relational operators for bool and tristate symbols
Since commit 31847b67bec0 ("kconfig: allow use of relations other than
(in)equality") it is possible to use relational operators in Kconfig
statements. However, those operators give unexpected results when
applied to bool/tristate values:
(n < y) = y (correct)
(m < y) = y (correct)
(n < m) = n (wrong)
This happens because relational operators process bool and tristate
symbols as strings and m sorts before n. It makes little sense to do a
lexicographical compare on bool and tristate values though.
Documentation/kbuild/kconfig-language.txt states that expression can have
a value of 'n', 'm' or 'y' (or 0, 1, 2 respectively for calculations).
Let's make it so for relational comparisons with bool/tristate
expressions as well and document them. If at least one symbol is an
actual string then the lexicographical compare works just as before.
Signed-off-by: Nicolas Pitre <nico@linaro.org>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
Tested-by: Randy Dunlap <rdunlap@infradead.org>
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Diffstat (limited to 'scripts/genksyms/parse.tab.c_shipped')
0 files changed, 0 insertions, 0 deletions