From: Andreas Ruprecht <andreas.ruprecht@fau.de>
To: Ulf Magnusson <ulfalizer.lkml@gmail.com>
Cc: Paul Bolle <pebolle@tiscali.nl>,
Valentin Rothberg <valentinrothberg@gmail.com>,
rafael.j.wysocki@intel.com,
KCONFIG <linux-kbuild@vger.kernel.org>,
Kernel Mailing List <linux-kernel@vger.kernel.org>,
hengelein Stefan <stefan.hengelein@fau.de>,
linux@dominikbrodowski.net, Michal Marek <mmarek@suse.cz>
Subject: Re: [PATCH 1/2] kconfig: also warn of unhandled characters in statements
Date: Wed, 08 Jul 2015 12:17:30 +0200 [thread overview]
Message-ID: <559CF8BA.90803@fau.de> (raw)
In-Reply-To: <20150707144559.GA12760@huvuddator>
Hi,
On 07/07/2015 16:45, Ulf Magnusson wrote:
>
> Did you use the (undocumented, obviously :) REGENERATE_PARSERS option,
> like 'make menuconfig REGENERATE_PARSERS=1'? It's from
> scripts/Makefile.lib.
>
> The following patch works fine for me from some quick experimentation.
> It's against the mainline kernel, as for some reason I can't clone
> git://gitorious.org/linux-kconfig/linux-kconfig at the moment.
yep, I used that. After some playing around with it, I also submitted a
v2 of the patch (although with the '-' still included in the regex for
PARAMs), didn't you receive that? (Message-Id:
<cover.1436264921.git.andreas.ruprecht@fau.de>) and the two patches as
replies to the cover letter. They are against yesterday's linux-next.
Regards,
Andreas
next prev parent reply other threads:[~2015-07-08 10:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-03 12:46 [PATCH 0/2] kconfig: " Andreas Ruprecht
2015-07-03 12:46 ` [PATCH 1/2] kconfig: also " Andreas Ruprecht
2015-07-04 9:33 ` Paul Bolle
2015-07-05 6:44 ` Ulf Magnusson
2015-07-05 6:06 ` Ulf Magnusson
[not found] ` <559BA09A.2030603@fau.de>
[not found] ` <20150707144559.GA12760@huvuddator>
2015-07-08 10:17 ` Andreas Ruprecht [this message]
2015-07-08 20:18 ` Ulf Magnusson
2015-07-03 12:46 ` [PATCH 2/2] kconfig: Regenerate shipped zconf.lex.c file Andreas Ruprecht
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=559CF8BA.90803@fau.de \
--to=andreas.ruprecht@fau.de \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=mmarek@suse.cz \
--cc=pebolle@tiscali.nl \
--cc=rafael.j.wysocki@intel.com \
--cc=stefan.hengelein@fau.de \
--cc=ulfalizer.lkml@gmail.com \
--cc=valentinrothberg@gmail.com \
/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
Powered by JetHome