public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Dirk Gouders <dirk@gouders.net>
To: Martin Walch <walch.martin@web.de>
Cc: "Yann E. MORIN" <yann.morin.1998@free.fr>,
	linux-kbuild@vger.kernel.org, "Michal Marek" <mmarek@suse.cz>,
	"Jiri Kosina" <trivial@kernel.org>,
	"Arve Hjønnevåg" <arve@android.com>,
	"Benjamin Poirier" <bpoirier@suse.de>,
	"Wang YanQing" <udknight@gmail.com>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"Jean Delvare" <jdelvare@suse.de>,
	"Kees Cook" <keescook@chromium.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/4] kconfig: remove unused definition from scanner
Date: Thu, 03 Oct 2013 15:13:09 +0200	[thread overview]
Message-ID: <ghsiwia462.fsf@lena.gouders.net> (raw)
In-Reply-To: <1491733.iNaKkFyqph@tacticalops> (Martin Walch's message of "Thu, 03 Oct 2013 02:30:21 +0200")

[-- Attachment #1: Type: text/plain, Size: 1092 bytes --]

Martin Walch <walch.martin@web.de> writes:

> On Wednesday 02 October 2013 08:57:54 Yann E. MORIN wrote:
>> On Wednesday 02 October 2013 08:42:59 Dirk Gouders wrote:
>> > I think you should also regenerate the scanner and add
>> > the new zconf.lex.c_shipped to this patch.
>> 
>> I think sending the re-generated parser as a separate patch helps
>> in reviewing. Ie. I'd prefer a fifth patch.
>> 
>> BTW, regenerating the parser can be done with:
>>     make REGENERATE_PARSERS=1 config
>
> Actually, I regenerated the scanner. However, the results did not change
> after applying the patch, because the definition that the patch removes
> (ws) is not used anywhere. It is only a cleanup.

Sorry, my review was too superficial.
I did downgrade my flex to see if your changes affect the scanner,
but I did not test it without your patch and also did not have a look in
what the changes are.

The changes I noticed here are probably related to the flex package I
use (on a Gentoo system) -- they even occur without your patch.  I'll
attach what I noticed in case someone is interested.

Dirk


[-- Attachment #2: zconf.lex.c_shipped.patch --]
[-- Type: text/plain, Size: 583 bytes --]

diff --git a/scripts/kconfig/zconf.lex.c_shipped b/scripts/kconfig/zconf.lex.c_shipped
index a0521aa..3eb4c0b 100644
--- a/scripts/kconfig/zconf.lex.c_shipped
+++ b/scripts/kconfig/zconf.lex.c_shipped
@@ -920,7 +920,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,

      parent reply	other threads:[~2013-10-03 13:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-02  5:24 [PATCH 4/4] kconfig: remove unused definition from scanner Martin Walch
2013-10-02  6:42 ` Dirk Gouders
2013-10-02  6:57   ` Yann E. MORIN
2013-10-03  0:30     ` Martin Walch
2013-10-03  6:37       ` Yann E. MORIN
2013-10-03 13:13       ` Dirk Gouders [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=ghsiwia462.fsf@lena.gouders.net \
    --to=dirk@gouders.net \
    --cc=akpm@linux-foundation.org \
    --cc=arve@android.com \
    --cc=bpoirier@suse.de \
    --cc=jdelvare@suse.de \
    --cc=keescook@chromium.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmarek@suse.cz \
    --cc=trivial@kernel.org \
    --cc=udknight@gmail.com \
    --cc=walch.martin@web.de \
    --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