From: Paul Bolle <pebolle@tiscali.nl>
To: Christoph Jaeger <cj@linux.com>
Cc: yann.morin.1998@free.fr, linux-kbuild@vger.kernel.org,
linux-kernel@vger.kernel.org, dborkman@redhat.com
Subject: Re: [PATCH 1/3] kconfig: regenerate parser
Date: Mon, 08 Dec 2014 21:28:27 +0100 [thread overview]
Message-ID: <1418070507.2058.46.camel@x220> (raw)
In-Reply-To: <0bf50ad9bc78f6944ebf5d5b1f8c9bdff223185f.1418003065.git.cj@linux.com>
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@linux.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@tiscali.nl>
Paul Bolle
next prev parent reply other threads:[~2014-12-08 20:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-08 1:49 [PATCH 0/3] remove undocumented type definition alias Christoph Jaeger
2014-12-08 1:49 ` [PATCH 1/3] kconfig: regenerate parser Christoph Jaeger
2014-12-08 20:28 ` Paul Bolle [this message]
2014-12-08 1:49 ` [PATCH 2/3] kconfig: remove undocumented type definition alias 'boolean' Christoph Jaeger
2014-12-08 18:51 ` Paul Bolle
2014-12-08 19:13 ` Paul Bolle
2014-12-08 19:16 ` Daniel Borkmann
2014-12-08 19:41 ` Paul Bolle
2014-12-08 20:36 ` Paul Bolle
2014-12-08 21:15 ` Paul Bolle
2014-12-09 11:49 ` Daniel Borkmann
2014-12-09 23:14 ` Christoph Jaeger
2014-12-08 1:49 ` [PATCH 3/3] kconfig: rename S_BOOLEAN to S_BOOL for consistency Christoph Jaeger
2014-12-08 20:43 ` Paul Bolle
2014-12-08 20:20 ` [PATCH 0/3] remove undocumented type definition alias Paul Bolle
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=1418070507.2058.46.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=cj@linux.com \
--cc=dborkman@redhat.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.