[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1491733.iNaKkFyqph@tacticalops>
Date: Thu, 03 Oct 2013 02:30:21 +0200
From: Martin Walch <walch.martin@....de>
To: "Yann E. MORIN" <yann.morin.1998@...e.fr>,
linux-kbuild@...r.kernel.org
Cc: Dirk Gouders <dirk@...ders.net>, Michal Marek <mmarek@...e.cz>,
Jiri Kosina <trivial@...nel.org>,
Arve Hjønnevåg <arve@...roid.com>,
Benjamin Poirier <bpoirier@...e.de>,
Wang YanQing <udknight@...il.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Jean Delvare <jdelvare@...e.de>,
Kees Cook <keescook@...omium.org>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 4/4] kconfig: remove unused definition from scanner
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.
Regenerating the scanner and the parser code with newer versions of
flex and bison results in code changes. However, they are not related to
the patch, but originate from updates in flex and bison.
Therefore I did not see any point in including the regenerated files in
this patch set.
Of course, if you see any benefit in regenerating the *_shipped files, I can
still do so.
Regards,
Martin Walch
--
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists