kconfig: clean up EOF handling in the lexer

A new file should always start in the INITIAL state.

When the lexer bumps into EOF, the lexer must get back to the INITIAL
state anyway. Remove the redundant <<EOF>> pattern in the PARAM state.

Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>

diff --git a/scripts/kconfig/zconf.l b/scripts/kconfig/zconf.l
index 847ba4248092854c48bcada6fc4a30c3af26665b..9038e9736bf03cf489ab50d1348e429d3885268a 100644 (file)
--- a/scripts/kconfig/zconf.l
+++ b/scripts/kconfig/zconf.l
@@ -178,9 +178,6 @@ n   [A-Za-z0-9_-]
        \\\n    ;
        [[:blank:]]+
        .       warn_ignored_character(*yytext);
        \\\n    ;
        [[:blank:]]+
        .       warn_ignored_character(*yytext);

-       <<EOF>> {
-               BEGIN(INITIAL);
-       }

 }
 
 <STRING>{
 }
 
 <STRING>{


@@ -262,6 +259,8 @@ n   [A-Za-z0-9_-]
 }
 
 <<EOF>>        {
 }
 
 <<EOF>>        {

+       BEGIN(INITIAL);
+

        if (current_file) {
                zconf_endfile();
                return T_EOL;
        if (current_file) {
                zconf_endfile();
                return T_EOL;