From: Paul Bolle <pebolle@tiscali.nl>
To: Jan Beulich <JBeulich@suse.com>
Cc: linux-kbuild@vger.kernel.org, akpm@linux-foundation.org,
Michal Marek <mmarek@suse.cz>
Subject: Re: [PATCH v2 1/2] kconfig: don't silently ignore unhandled characters
Date: Fri, 16 Jan 2015 17:25:32 +0100 [thread overview]
Message-ID: <1421425532.8562.32.camel@x220> (raw)
In-Reply-To: <54B93FE60200007800055E84@mail.emea.novell.com>
On Fri, 2015-01-16 at 15:44 +0000, Jan Beulich wrote:
> At the very least we should tell people that waht they wrote is not
what
> what the utility understands.
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
> Acked-by: Paul Bolle <pebolle@tiscali.nl>
> ---
> v2: printf() -> fprintf(stderr, ) upon Paul Bolle's request. Replace
> two instances of double backslash line continuations with single
> ones in sound/soc/intel/Kconfig.
> ---
> scripts/kconfig/zconf.l | 7 +
> scripts/kconfig/zconf.lex.c_shipped | 195 +++++++++++++++++++-----------------
> sound/soc/intel/Kconfig | 4
I guess Michal would like to split the c_shipped changes in this patch
too. (I personally don't care.) And I think the sound/soc/intel/Kconfig
should be a separate patch.
> 3 files changed, 115 insertions(+), 91 deletions(-)
>
> --- 3.19-rc4-kconfig.orig/scripts/kconfig/zconf.l
> +++ 3.19-rc4-kconfig/scripts/kconfig/zconf.l
> @@ -141,7 +141,12 @@ n [A-Za-z0-9_]
> }
> #.* /* comment */
> \\\n current_file->lineno++;
> - .
> + [[:blank:]]+
> + . {
(Side note: I can't read lex, so is there a reason the dot is on a new
line? And I'm lazy too: what happens if you drop "[[:blank:]]+". In
other words: why was it added?)
> + fprintf(stderr,
> + "%s:%d:warning: ignoring unsupported character '%c'\n",
> + zconf_curname(), zconf_lineno(), *yytext);
> + }
> <<EOF>> {
> BEGIN(INITIAL);
> }
Thanks!
Paul Bolle
next prev parent reply other threads:[~2015-01-16 16:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-16 15:44 [PATCH v2 1/2] kconfig: don't silently ignore unhandled characters Jan Beulich
2015-01-16 16:25 ` Paul Bolle [this message]
2015-01-16 16:32 ` Jan Beulich
2015-01-16 17:53 ` Paul Bolle
2015-01-19 10:28 ` Jiri Kosina
2015-01-19 12:50 ` Michal Marek
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=1421425532.8562.32.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=JBeulich@suse.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=mmarek@suse.cz \
/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