[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1435829132.2423.10.camel@tiscali.nl>
Date: Thu, 02 Jul 2015 11:25:32 +0200
From: Paul Bolle <pebolle@...cali.nl>
To: Valentin Rothberg <valentinrothberg@...il.com>
Cc: rafael.j.wysocki@...el.com, linux-kbuild@...r.kernel.org,
linux-kernel@...r.kernel.org,
Andreas Ruprecht <andreas.ruprecht@....de>,
hengelein Stefan <stefan.hengelein@....de>,
linux@...inikbrodowski.net
Subject: Re: Kconfig: '+config' valid syntax?
On do, 2015-07-02 at 11:01 +0200, Paul Bolle wrote:
> I'm just guessing here. Anyhow, you might start by looking at this
> snippet in zconf.l:
> . {
> unput(yytext[0]);
> BEGIN(COMMAND);
> }
>
>
> <COMMAND>{
> {n}+ {
> [...]
> }
> .
> \n {
> BEGIN(INITIAL);
> current_file->lineno++;
> return T_EOL;
> }
> }
>
> Which perhaps translates to:
> - ignore unknown stuff for now and go in COMMAND state;
> - do something if we encounter some text ({n} = [A-Za-z0-9_]);
> - go in INITIAL state if we encounter newlines or unknown stuff.
>
> At the end of which we're back where we started before encountering
> the'+'. But there are more references to '.' in the lex rules so it's
> probably more complicated.
All of which is moot after commit 2e0d737fc76f ("kconfig: don't silently
ignore unhandled characters"). That's in linux-next but not (yet) in
v4.1+. It even has my Ack! My memory really must be degrading now...
Paul Bolle
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists