diff options
author | Masahiro Yamada <yamada.masahiro@socionext.com> | 2018-12-11 20:01:10 +0900 |
---|---|---|
committer | Masahiro Yamada <yamada.masahiro@socionext.com> | 2018-12-28 20:44:38 +0900 |
commit | 979f2b2f7936f4b71a3100baf2d16c8057f027eb (patch) | |
tree | 02cc885fdf217e12d7cea210136a04fedf206667 /scripts/gdb | |
parent | 4b31a32caf0a28e4726f1bf267ff8a804ed864e2 (diff) | |
download | linux-979f2b2f7936f4b71a3100baf2d16c8057f027eb.tar.gz linux-979f2b2f7936f4b71a3100baf2d16c8057f027eb.tar.bz2 linux-979f2b2f7936f4b71a3100baf2d16c8057f027eb.zip |
kconfig: remove keyword lookup table entirely
Commit 7a88488bbc23 ("[PATCH] kconfig: use gperf for kconfig keywords")
introduced gperf for the keyword lookup.
Then, commit bb3290d91695 ("Remove gperf usage from toolchain") killed
the gperf use. As a result, the linear keyword search was left behind.
If we do not use gperf, there is no reason to have the separate table
of the keywords. Move all keywords back to the lexer.
I also refactored the lexer to remove the COMMAND and PARAM states.
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Diffstat (limited to 'scripts/gdb')
0 files changed, 0 insertions, 0 deletions