From: Michal Marek <mmarek@suse.cz>
To: Ulf Magnusson <ulfalizer.lkml@gmail.com>,
Andreas Ruprecht <andreas.ruprecht@fau.de>
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
Subject: Re: [PATCH v4 0/2] kconfig: warn of unhandled characters in Kconfig commands
Date: Wed, 19 Aug 2015 17:06:56 +0200 [thread overview]
Message-ID: <55D49B90.4060906@suse.cz> (raw)
In-Reply-To: <20150720085414.GA32583@huvuddator>
On 2015-07-20 10:54, Ulf Magnusson wrote:
> On Sun, Jul 12, 2015 at 09:41:49AM +0200, Andreas Ruprecht wrote:
>> 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 '---help---' separately.
>>
>> Changes to v1:
>> - add '---help---' in zconf.gperf instead of special casing
>> it in zconf.l
>>
>> Changes to v2:
>> - Do no constify char parameter to warn_ignored_character
>> - Shorten rule definitions for '.'
>>
>> Changes to v3:
>> - spaces -> tabs in zconf.gperf
>>
>> Andreas Ruprecht (2):
>> kconfig: warn of unhandled characters in Kconfig commands
>> kconfig: Regenerate shipped zconf.{hash,lex}.c files
>>
>> scripts/kconfig/zconf.gperf | 1 +
>> scripts/kconfig/zconf.hash.c_shipped | 58 ++++---
>> scripts/kconfig/zconf.l | 20 ++-
>> scripts/kconfig/zconf.lex.c_shipped | 325 +++++++++++++++++------------------
>> 4 files changed, 204 insertions(+), 200 deletions(-)
>>
>> --
>> 1.9.1
>>
>
> For what it's worth:
>
> Reviewed-by: Ulf Magnusson <ulfalizer@gmail.com>
> Tested-by: Ulf Magnusson <ulfalizer@gmail.com>
Applied to kbuild.git#kconfig.
Michal
prev parent reply other threads:[~2015-08-19 15:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-12 7:41 [PATCH v4 0/2] kconfig: warn of unhandled characters in Kconfig commands Andreas Ruprecht
2015-07-12 7:41 ` [PATCH v4 1/2] " Andreas Ruprecht
2015-07-12 7:41 ` [PATCH v4 2/2] kconfig: Regenerate shipped zconf.{hash,lex}.c files Andreas Ruprecht
2015-07-20 8:54 ` [PATCH v4 0/2] kconfig: warn of unhandled characters in Kconfig commands Ulf Magnusson
2015-08-19 15:06 ` Michal Marek [this message]
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=55D49B90.4060906@suse.cz \
--to=mmarek@suse.cz \
--cc=andreas.ruprecht@fau.de \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--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).