public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Bolle <pebolle@tiscali.nl>
To: Jan Beulich <JBeulich@suse.com>
Cc: yann.morin.1998@free.fr, linux-kbuild@vger.kernel.org
Subject: Re: [PATCH 1/2] kconfig: don't silently ignore unhandled characters
Date: Wed, 05 Nov 2014 11:36:29 +0100	[thread overview]
Message-ID: <1415183789.20372.243.camel@x220> (raw)
In-Reply-To: <5458ED470200007800044DA7@mail.emea.novell.com>

On Tue, 2014-11-04 at 14:14 +0000, Jan Beulich wrote:
> >>> On 04.11.14 at 15:06, <pebolle@tiscali.nl> wrote:
> > On Tue, 2014-11-04 at 09:05 +0000, Jan Beulich wrote:
> >> @@ -920,7 +931,7 @@ static int input (void );
> >>  /* This used to be an fputs(), but since the string might contain NUL's,
> >>   * we now use fwrite().
> >>   */
> >> -#define ECHO do { if (fwrite( zconftext, zconfleng, 1, zconfout )) {} } while (0)
> >> +#define ECHO fwrite( zconftext, zconfleng, 1, zconfout )
> >>  #endif
> >>  
> >>  /* Gets input and stuffs it into "buf".  number of characters read, or YY_NULL,
> > 
> > But this hunk looks unrelated. Is this needed?
> 
> I think it should stay, even if my flex version may be slightly different
> from the one that was used originally. As above - it's simply a result
> of re-generating.

(This annoyed me enough to dive a bit deeper. This message is mainly to
archive my notes publicly.)

This #define was added in v3.1. See commit 2f76b358f9fb ("kconfig: regen
parser"). Commit explanations were probably a bit expensive then since
this is all the info we have: we don't know why this was done, nor how
(which program, which options, etc.).

Anyhow, I don't think ECHO is used anywhere. grepping for ECHO in
scripts/ finds dtc-lexer.lex.c_shipped, lex.lex.c_shipped, and this
file. In the other two _shipped files ECHO is actually used. So,
apparently it's not a bit of lex magic. The #define might as well be
removed.

I personally wouldn't bother to add this hunk, but who cares.


Paul Bolle


  reply	other threads:[~2014-11-05 10:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-04  9:05 [PATCH 1/2] kconfig: don't silently ignore unhandled characters Jan Beulich
2014-11-04 14:06 ` Paul Bolle
2014-11-04 14:14   ` Jan Beulich
2014-11-05 10:36     ` Paul Bolle [this message]
2014-11-06 10:19       ` Jan Beulich
2014-11-06 10:28         ` Paul Bolle
2014-12-09 10:16     ` Paul Bolle
2014-12-19 16:31       ` Jan Beulich

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=1415183789.20372.243.camel@x220 \
    --to=pebolle@tiscali.nl \
    --cc=JBeulich@suse.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=yann.morin.1998@free.fr \
    /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