[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1418070507.2058.46.camel@x220>
Date: Mon, 08 Dec 2014 21:28:27 +0100
From: Paul Bolle <pebolle@...cali.nl>
To: Christoph Jaeger <cj@...ux.com>
Cc: yann.morin.1998@...e.fr, linux-kbuild@...r.kernel.org,
linux-kernel@...r.kernel.org, dborkman@...hat.com
Subject: Re: [PATCH 1/3] kconfig: regenerate parser
On Sun, 2014-12-07 at 20:49 -0500, Christoph Jaeger wrote:
> Regenerate the Kconfig parser with Bison 3.0.2 in preparation for a following
Nit: could you please add the exact command line too?
> commit. Otherwise the changes caused by the more recent Bison version would be
> intermingled with functional changes.
>
> Signed-off-by: Christoph Jaeger <cj@...ux.com>
> ---
Are there any downsides to regenerating using, what looks like, a
current version of bison? I'm not aware there are.
I've tested this on all 463 defconfig files in next-20141208. None of
the generated .config files changed. So this patch is:
Tested-by: Paul Bolle <pebolle@...cali.nl>
Paul Bolle
--
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