From: Andreas Ruprecht <andreas.ruprecht@fau.de>
To: Ulf Magnusson <ulfalizer.lkml@gmail.com>
Cc: Paul Bolle <pebolle@tiscali.nl>,
Valentin Rothberg <valentinrothberg@gmail.com>,
rafael.j.wysocki@intel.com, <linux-kbuild@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
hengelein Stefan <stefan.hengelein@fau.de>,
linux@dominikbrodowski.net, Michal Marek <mmarek@suse.cz>,
Andreas Ruprecht <andreas.ruprecht@fau.de>
Subject: [PATCH 0/2] kconfig: warn of unhandled characters in statements
Date: Fri, 3 Jul 2015 14:46:37 +0200 [thread overview]
Message-ID: <cover.1435927467.git.andreas.ruprecht@fau.de> (raw)
This patchset changes the lexer file to emit a warning if any unhandled
characters are found in the input. So far, Kconfig options like
+config FOO
bool
[...]
(note the wrong '+'!) were parsed without a warning. As simply adding a
warning for '.' produces lots of warnings as occasionally '---help---'
is used instead of 'help' (and thus '-' is recognized as an unhandled
character), we need to handle the former separately.
Andreas Ruprecht (2):
kconfig: also warn of unhandled characters in statements
kconfig: Regenerate shipped zconf.lex.c file
scripts/kconfig/zconf.l | 11 +-
scripts/kconfig/zconf.lex.c_shipped | 453 +++++++++++++++++++++++++-----------
2 files changed, 322 insertions(+), 142 deletions(-)
--
1.9.1
next reply other threads:[~2015-07-03 12:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-03 12:46 Andreas Ruprecht [this message]
2015-07-03 12:46 ` [PATCH 1/2] kconfig: also warn of unhandled characters in statements Andreas Ruprecht
2015-07-04 9:33 ` Paul Bolle
2015-07-05 6:44 ` Ulf Magnusson
2015-07-05 6:06 ` Ulf Magnusson
[not found] ` <559BA09A.2030603@fau.de>
[not found] ` <20150707144559.GA12760@huvuddator>
2015-07-08 10:17 ` Andreas Ruprecht
2015-07-08 20:18 ` Ulf Magnusson
2015-07-03 12:46 ` [PATCH 2/2] kconfig: Regenerate shipped zconf.lex.c file Andreas Ruprecht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1435927467.git.andreas.ruprecht@fau.de \
--to=andreas.ruprecht@fau.de \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=mmarek@suse.cz \
--cc=pebolle@tiscali.nl \
--cc=rafael.j.wysocki@intel.com \
--cc=stefan.hengelein@fau.de \
--cc=ulfalizer.lkml@gmail.com \
--cc=valentinrothberg@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).